Subject: Re: maple_attach_dev
To: Jason R Thorpe <thorpej@zembu.com>
From: Joseph Mallett <jmallett@newgold.net>
List: port-dreamcast
Date: 03/17/2001 14:42:43
Seems to me that using a devfs-like thing in this situation would work
best... ie:

/dev/maple/devicen

where n is a 0 offset number

and IF it is recognised, it becomes

/dev/maple/keyboard

or something.

But I'm just spoiled and like devfs lol.

/joseph

--
Joseph Mallett
+1 919 349 2976
6709 Valley Woods Ln
Apex NC 27502
http://newgold.net/
http://xMach.org/

On Sat, 17 Mar 2001, Jason R Thorpe wrote:

> On Sat, Mar 17, 2001 at 08:09:51PM +0100, Marcus Comstedt wrote:
> 
>  > Yes, that sounds like what I would like to have.  So if these can be
>  > provided directly by the "maple" driver, then I guess we don't need
>  > the "mmf" driver at all?
> 
> No, you still want the "mmf" layer to attach "found" devices at a
> given port/subunit to, which would then attach e.g. mkbd, mms, mctlr,
> etc. to each of its functions.
> 
> It's similar to how the original 4.4BSD/sparc SCSI code worked (attached
> a "target" to each found target, and then attached "sd", "st", etc. to
> each LUN on the target).
> 
> -- 
>         -- Jason R. Thorpe <thorpej@zembu.com>
>