Re: [QUESTIONS] Transision from pcmcia-cs to 2.4 built-in PCMCIA
[EMAIL PROTECTED] said: > First, why have I stopped needing cs and cb_enabler? cs is built into pcmcia_core.o, cb_enabler should still be there though. It's feasible that you only need cb_enabler for the old CardBus drivers, though - I'm not sure. > Second, why is yenta_socket only compiled if I enable CardBus support > in the kernel? I'm running an Orinoco card on another machine, and > since I don't think it's CardBus (am I wrong?), I didn't enable CB in > the kernel. The i82365 driver is the only one compiled, but it seems > to work fine on that machine. Should I enable CardBus support and use > yenta_socket instead? yenta_socket is the driver for CardBus i82365-compatible sockets. i82365 no longer drives CardBus sockets, only PCMCIA. > Third, on the first machine with both cards, neither card works if I > use i82365 instead of yenta_socket, why? The Orinoco gets Tx timeouts > on every packet, and inserting the 3c595 causes the controller > (socket) to time out waiting for reset and it doesn't recognize the > 3c595. The PCMCIA card ought to work. It's probably screwed up the IRQ routing - it no longer knows about some of the differences between CardBus and PCMCIA bridges. What exactly is the bridge in this machine? -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [QUESTIONS] Transision from pcmcia-cs to 2.4 built-in PCMCIA
[EMAIL PROTECTED] said: First, why have I stopped needing cs and cb_enabler? cs is built into pcmcia_core.o, cb_enabler should still be there though. It's feasible that you only need cb_enabler for the old CardBus drivers, though - I'm not sure. Second, why is yenta_socket only compiled if I enable CardBus support in the kernel? I'm running an Orinoco card on another machine, and since I don't think it's CardBus (am I wrong?), I didn't enable CB in the kernel. The i82365 driver is the only one compiled, but it seems to work fine on that machine. Should I enable CardBus support and use yenta_socket instead? yenta_socket is the driver for CardBus i82365-compatible sockets. i82365 no longer drives CardBus sockets, only PCMCIA. Third, on the first machine with both cards, neither card works if I use i82365 instead of yenta_socket, why? The Orinoco gets Tx timeouts on every packet, and inserting the 3c595 causes the controller (socket) to time out waiting for reset and it doesn't recognize the 3c595. The PCMCIA card ought to work. It's probably screwed up the IRQ routing - it no longer knows about some of the differences between CardBus and PCMCIA bridges. What exactly is the bridge in this machine? -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[QUESTIONS] Transision from pcmcia-cs to 2.4 built-in PCMCIA
I have a 3c595 CardBus card and a Lucent Orinoco card under pcmcia-cs I used the following drivers: pcmcia_core, ds, and (I think) cs for low level stuff, i82365 for the controller, cb_enabler and 3c595_cb for the 3c595, and wvlan_cs for the Orinoco under the kernel pcmcia support, I use: pcmcia_core and ds for low level stuff, yenta_socket for the controller, 3c59x (same driver as PCI) for the 3c595, and hermes and orinoco_cs for the Orinoco Now after awhile I figured out what new drivers I should start using, but I have a few things about the change that still confuse me... First, why have I stopped needing cs and cb_enabler? Second, why is yenta_socket only compiled if I enable CardBus support in the kernel? I'm running an Orinoco card on another machine, and since I don't think it's CardBus (am I wrong?), I didn't enable CB in the kernel. The i82365 driver is the only one compiled, but it seems to work fine on that machine. Should I enable CardBus support and use yenta_socket instead? Third, on the first machine with both cards, neither card works if I use i82365 instead of yenta_socket, why? The Orinoco gets Tx timeouts on every packet, and inserting the 3c595 causes the controller (socket) to time out waiting for reset and it doesn't recognize the 3c595. Despite the confusion of changing systems, I must say that the orinoco driver works much better than wvlan_cs for me, as the two Orinoco cards in IBSS Ad-Hoc mode would get intermittent Tx timeouts with the wvlan_cs driver. It's also nice not to have to rebuild pcmcia-cs when I upgrade my kernel anymore. Keep up the good work! Ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[QUESTIONS] Transision from pcmcia-cs to 2.4 built-in PCMCIA
I have a 3c595 CardBus card and a Lucent Orinoco card under pcmcia-cs I used the following drivers: pcmcia_core, ds, and (I think) cs for low level stuff, i82365 for the controller, cb_enabler and 3c595_cb for the 3c595, and wvlan_cs for the Orinoco under the kernel pcmcia support, I use: pcmcia_core and ds for low level stuff, yenta_socket for the controller, 3c59x (same driver as PCI) for the 3c595, and hermes and orinoco_cs for the Orinoco Now after awhile I figured out what new drivers I should start using, but I have a few things about the change that still confuse me... First, why have I stopped needing cs and cb_enabler? Second, why is yenta_socket only compiled if I enable CardBus support in the kernel? I'm running an Orinoco card on another machine, and since I don't think it's CardBus (am I wrong?), I didn't enable CB in the kernel. The i82365 driver is the only one compiled, but it seems to work fine on that machine. Should I enable CardBus support and use yenta_socket instead? Third, on the first machine with both cards, neither card works if I use i82365 instead of yenta_socket, why? The Orinoco gets Tx timeouts on every packet, and inserting the 3c595 causes the controller (socket) to time out waiting for reset and it doesn't recognize the 3c595. Despite the confusion of changing systems, I must say that the orinoco driver works much better than wvlan_cs for me, as the two Orinoco cards in IBSS Ad-Hoc mode would get intermittent Tx timeouts with the wvlan_cs driver. It's also nice not to have to rebuild pcmcia-cs when I upgrade my kernel anymore. Keep up the good work! Ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
