bug-commoncpp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hardware API for CommonC++


From: David Sugar
Subject: Re: Hardware API for CommonC++
Date: Thu, 11 Dec 2003 06:41:36 -0500
User-agent: KMail/1.5.3

This seems generally useful then.  Yes, I think we can fit it in somewhere for 
a future release, once cvs comes back alive.

On Monday 08 December 2003 03:07 pm, Marc Boris Dürner wrote:
> On Monday 08 December 2003 20:59, you wrote:
> > I think it would be very interesting, and I could see several places and
> > possible projects I would use something like this already, so yes, I
> > think
> >
> > it could be a very good addition.  How portable is this?  Is it very
> > specific GNU/Linux, or can it be used/easily adapted for use with other
> > operating systems and kernels, such FreeBSD for example?
>
> I see it as a backend for freedesktop.org's HAL, which has to get away from
> ugly C  ;)
>
> It should be fairly portable. The PCI and USB stuff comes with its own
> parser for the
> configuration registers for example, so in theory all you have to do is
> point them to
> wherever the registers reside. Sometimes you may get them with an ioctl()
> or from a FS
> like procfs. I am going to write a parser for pcmcia too, but the specs
> seem not to be
> openly accessible. I could only get the usb and pci specs for free. however
> there is parsing
> code from the linux kernel I have seen and could modify. It might even be
> portable
> without a pcmcia parser since the most Unix-like OS`es are similar in how
> to get the data
> from the pcmcia configuration space.
>
> As for implementing the iostreams it will be as difficult as say libusb,
> which wraps up the
> different API`s. I (we) have to make a descision how to implement them. I
> was a bit
> reluctant to use too many C++ features in the beginning, as I dreamt of
> having it in
> EmbeddedC++ and maybe include driver/kernel stuff one day, but I have given
> up on this
> dream, since the current political situtation, at least in the linux world,
> will prevent any nice
> C++ interfaces in the kernel in the foreseeable future.
>
> Its not meant to be GNU/Linux specific. I would certainly appreciate help
> from the BSD and
> Hurd people and I try as hard as I can to stay away from any linux-isms.
>
> Are there any other modules planned for CommonC++? I have never heard of it
> before,
> even though it packages a lot of very useful stuff. What are the other
> plany for the future?
> Modularisation maybe?
>
> regards,
> Marc





reply via email to

[Prev in Thread] Current Thread [Next in Thread]