Joerg Schilling wrote:
> "Garrett D'Amore" <[EMAIL PROTECTED]> wrote:
>
>   
>> If I had a device driver that, for reasons I won't go into here, needed 
>> to be STREAMS, could I then add a devmap(9E) entry point to additionally 
>> support mmap(2)?  (The problem is that for my project, I may have to 
>> support two different semantics -- one which relies on STREAMS, the 
>> other which must support mmap(2).)
>>     
>
> If you did ask this 12 years ago, it was easier for me to answer ;-)
>
> 1)    It works/worked, for many ATM DLPI drivers to download the firmware 
>       from userland.
>
> 2)    You will get into problems if you have more than one instance on
>       your system:
>
>       2a)     IIRC, You have to return a PTE early at driver attach time
>               before you know the instance number. Solution: return
>               a dummy number and send a correct number later on
>
>       2b)     You may need to do some additional tricks if instance #0
>               is not present (See 2a).
>
> The FORE ATM driver did it wrong and was unable to deal with a moved ATM 
> card untill you manually edited the file /etc/path_to_inst and removed the
> old instance data.
>   

Thanks, this is useful info.  It *sounds* like these issues are related 
to DLPI style 2 attach, which we don't have.  (When you open a sound 
device, it inherently has a node attached, more like a style 1 DLPI 
node.)  I'm going to play around with this and see what happens.

    -- Garrett

_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to