Re: PCMCIA drivers
> The current pccard code is evil and must die. Be that as it may, it is a huge improvement today over what it was a month ago. Thanks!! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCMCIA drivers
In messageAdam Wight writes: : First, the current zp driver cannot be configured if the pccard services : are being used, since it uses its own pccard code. Very Bad. : : Then, the PCMCIA model that we use now makes it impossible to use both : functions of a doubly useful card. This too is Very Bad. : : Is anyone addressing these problems? Yes. I'm working on porting the newconfig based pccard/cardbus code to -current. zp is evil and will die. The current pccard code is evil and must die. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PCMCIA drivers
I just started hacking the zp driver to support the 3Com 3C562 dual-function ether/modem card, and I wanted to make sure I'm not duplicating effort. While I'm at it, there are two significant design issues that I could use input on: First, the current zp driver cannot be configured if the pccard services are being used, since it uses its own pccard code. Very Bad. Then, the PCMCIA model that we use now makes it impossible to use both functions of a doubly useful card. This too is Very Bad. Is anyone addressing these problems? -Adam Wight To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message