On Tue, Aug 22, 2006 at 04:05:30PM +0300, Constantine Kousoulos wrote:
> Ok. So there are as many device_xxx() routines as the types of
> drivers that mach supports.
>
> How does mach choose the correct device_xxx() routine from the
> many available? Let's say that mach needs to acces the floppy
O/H Richard Braun έγραψε:
Actually, there is only one interface, the device_xxx() routines...
Ok. So there are as many device_xxx() routines as the types of
drivers that mach supports.
How does mach choose the correct device_xxx() routine from the
many available? Let's say that mach needs t
On Tue, Aug 22, 2006 at 01:49:01PM +0300, Constantine Kousoulos wrote:
> Hello,
>
> As it seems, mach has a "dual" device interface. Firstly, there
> is the native device interface (device_open, device_close etc).
> Secondly, there is the linux emulation device interface (again
> device_open, devi
Hello,
As it seems, mach has a "dual" device interface. Firstly, there
is the native device interface (device_open, device_close etc).
Secondly, there is the linux emulation device interface (again
device_open, device_close, etc in seperate files) that glues linux
drivers with mach.
How does mac
Thomas Schwinge <[EMAIL PROTECTED]> writes:
> If it's only problematic with respect to specific device drivers, I
> suggested to just leave out those, but as it seems, there are also
> infrastructure files like for isa bus access and general FreeBSD header
> file are affected, requiring advertisin
On Thu, Aug 03, 2006 at 10:31:39AM -0700, Thomas Bushnell BSG wrote:
> Richard Braun <[EMAIL PROTECTED]> writes:
> > On Tue, 25 Jul 2006 21:07:51 +0200, Richard Braun wrote:
> >> I have already begun working on it. Although I'm only begining, I've
> >> already managed to compile some drivers (they
Richard Braun <[EMAIL PROTECTED]> writes:
> On Tue, 25 Jul 2006 21:07:51 +0200, Richard Braun wrote:
>> I have already begun working on it. Although I'm only begining, I've
>> already managed to compile some drivers (they don't link yet).
>
> It looks like some important files are licensed under B
On Tue, 25 Jul 2006 21:07:51 +0200, Richard Braun wrote:
> I have already begun working on it. Although I'm only begining, I've
> already managed to compile some drivers (they don't link yet).
It looks like some important files are licensed under BSD-style licenses
with advertising clause. It comp
On Tue, Jul 25, 2006 at 09:57:38PM +0300, Constantine Kousoulos wrote:
> Personally, i am not biased towards porting freebsd or linux drivers.
> Using one or the other has its pros and cons. However, linux
> device drivers are better documented than than of freebsd's. I
> don't think that the freeb
I think it is clear that writing glue code is the way to go with
the current gnumach driver framework.
Personally, i am not biased towards porting freebsd or linux drivers.
Using one or the other has its pros and cons. However, linux
device drivers are better documented than than of freebsd's. I
On Mon, 17 Jul 2006 14:34:09 +0200
Richard Braun <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 17, 2006 at 02:35:51PM +0300, Constantine Kousoulos wrote:
> > In that way,
> > writing glue code is not very reusable. I could try writing
> > gnumach native drivers, although i'm not sure this is a better
>
On Mon, Jul 17, 2006 at 02:35:51PM +0300, Constantine Kousoulos wrote:
> In that way,
> writing glue code is not very reusable. I could try writing
> gnumach native drivers, although i'm not sure this is a better
> approach.
I disagree. Writing native drivers would take a *lot* of time. Just
consi
Hi,
Constantine Kousoulos, le Mon 17 Jul 2006 14:35:51 +0300, a écrit :
> However, since the linux kernel doesn't have a stable interface, it
> is very likely that if we would like to update gnumach's drivers in
> the near future, we would need to rewrite all over again the glue
> code. In that wa
Hello all,
Sometime ago, i posted a question on bug-hurd:
http://lists.gnu.org/archive/html/bug-hurd/2006-05/msg00040.html.
At that time, I decided to work on gnumach's device drivers but i
didn't announce it for a few reasons. First, i 'm no linux
kernel guru, so i needed time to explore the inn
Hello!
On Sun, Jul 16, 2006 at 06:49:23PM +0200, Richard Braun wrote:
> As a first step to implementing the sound system, it looks almost
> necessary to update the glue code.
Yes, that'll be needed as soon as you want to integrate most device
drivers that are newer than Linux 2.0's. A few newer
Hello,
As a first step to implementing the sound system, it looks almost
necessary to update the glue code. First, I'd like to know if anyone
has begun this work or intends to do it. Second, and if noone has
worked on this yet, what are the main steps and files to alter in
the gnumach-1-branch sou
16 matches
Mail list logo
