Re: Adding support for Duxbury PCI modem to FreeBSD 4.4
In message <[EMAIL PROTECTED]> Simon Dick writes: : So was I, I just found it advertised as Linux compatible and took a : gamble :) Cool. I've seen several that claimed that, but were not, in fact, actual controller based modems. Thanks for the chip info. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding support for Duxbury PCI modem to FreeBSD 4.4
On Tue, Oct 16, 2001 at 11:47:59AM -0600, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Simon Dick writes: > : Please don't remove the SurfRider one: > : sio0: port 0xa400-0xa407 irq 12 at device 10.0 on >pci0 > : sio0: moving to sio2 > : sio2: type 16550A > : > : It was me who submitted the ID for it, it's my main modem :) > > Wow! Cool. I didn't think that there were others. Do you know if > this is a "kermit" chipset or not? Is there a Lucent part on the card > with the word "kermit" on it (well, newer versions don't have kermit > on them). I didn't see any, here's what's on the various chips on it if this helps: 1) TOPIC TP560i 9935S14 D7S82.1 2) (my guess is a mem chip) HMC HM62H256DJ-12 9815A D84B1 3) The biggest chip on the board EON EN29F002NT -70P 0021 > I won't remove it. I was just surprised to find another one with the > plethera of winmodems. Cool. So was I, I just found it advertised as Linux compatible and took a gamble :) -- Simon Dick [EMAIL PROTECTED] "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding support for Duxbury PCI modem to FreeBSD 4.4
In message <[EMAIL PROTECTED]> Simon Dick writes: : Please don't remove the SurfRider one: : sio0: port 0xa400-0xa407 irq 12 at device 10.0 on pci0 : sio0: moving to sio2 : sio2: type 16550A : : It was me who submitted the ID for it, it's my main modem :) Wow! Cool. I didn't think that there were others. Do you know if this is a "kermit" chipset or not? Is there a Lucent part on the card with the word "kermit" on it (well, newer versions don't have kermit on them). I won't remove it. I was just surprised to find another one with the plethera of winmodems. Cool. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding support for Duxbury PCI modem to FreeBSD 4.4
On Tue, Oct 16, 2001 at 09:05:21AM -0600, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Matthew >Emmerton writes: > : On Tue, 16 Oct 2001, Peter van Heusden wrote: > : > : > On Mon, Oct 15, 2001 at 09:35:58AM -0600, Warner Losh wrote: > : > > In message ><[EMAIL PROTECTED]> "Peter van >Heusden" writes: > : > > : > I'm having a look at the Linux 2.4 kernel code, since they apparently > : > have winmodem support (including for the SM56 chipset, which is now > : > no longer supported by Motorola - double Aaaargh!), but will probably > : > have to go with an external modem, since it seems to be impossible to > : > get internal PCI non-winmodems. > : > : 3Com makes a PCI "hardware" (non-Winmodem) modem. > > I've seen only 3 hardware pci modems. All are based on the lucent > "kermit" chipset, but 3com PCI FaxModems have their own id. > > Well, I take that back. There's at least one pccard based pci modem. > There is a PLX part that glues the pccard bus to the pci ala some of > the wi adapters. And there's an old modem chipset on the card. These > were made out of surplus parts and I never saw them in real channels > (and to be honest, only consulted in writing a driver at the high > level for them, I've not put one in a machine or had one in hand). > > I'm not sure that the SurfRider that's listed in the driver really is > a hardware modem. All the other cards should likely be moved to my > puc bridge driver, but until I have that working, it is best to leave > things alone. :-) One problem with sio is that you can't have > different clock chip rates than the default. Some multiport boards > have faster xtals that allow higher data rates :-(. Please don't remove the SurfRider one: sio0: port 0xa400-0xa407 irq 12 at device 10.0 on pci0 sio0: moving to sio2 sio2: type 16550A It was me who submitted the ID for it, it's my main modem :) -- Simon Dick [EMAIL PROTECTED] "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding support for Duxbury PCI modem to FreeBSD 4.4
In message <[EMAIL PROTECTED]> Matthew Emmerton writes: : On Tue, 16 Oct 2001, Peter van Heusden wrote: : : > On Mon, Oct 15, 2001 at 09:35:58AM -0600, Warner Losh wrote: : > > In message <[EMAIL PROTECTED]> :"Peter van Heusden" writes: : > : > I'm having a look at the Linux 2.4 kernel code, since they apparently : > have winmodem support (including for the SM56 chipset, which is now : > no longer supported by Motorola - double Aaaargh!), but will probably : > have to go with an external modem, since it seems to be impossible to : > get internal PCI non-winmodems. : : 3Com makes a PCI "hardware" (non-Winmodem) modem. I've seen only 3 hardware pci modems. All are based on the lucent "kermit" chipset, but 3com PCI FaxModems have their own id. Well, I take that back. There's at least one pccard based pci modem. There is a PLX part that glues the pccard bus to the pci ala some of the wi adapters. And there's an old modem chipset on the card. These were made out of surplus parts and I never saw them in real channels (and to be honest, only consulted in writing a driver at the high level for them, I've not put one in a machine or had one in hand). I'm not sure that the SurfRider that's listed in the driver really is a hardware modem. All the other cards should likely be moved to my puc bridge driver, but until I have that working, it is best to leave things alone. :-) One problem with sio is that you can't have different clock chip rates than the default. Some multiport boards have faster xtals that allow higher data rates :-(. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding support for Duxbury PCI modem to FreeBSD 4.4
On Tue, 16 Oct 2001, Peter van Heusden wrote: > On Mon, Oct 15, 2001 at 09:35:58AM -0600, Warner Losh wrote: > > In message <[EMAIL PROTECTED]> >"Peter van Heusden" writes: > > I'm having a look at the Linux 2.4 kernel code, since they apparently > have winmodem support (including for the SM56 chipset, which is now > no longer supported by Motorola - double Aaaargh!), but will probably > have to go with an external modem, since it seems to be impossible to > get internal PCI non-winmodems. 3Com makes a PCI "hardware" (non-Winmodem) modem. -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding support for Duxbury PCI modem to FreeBSD 4.4
On Mon, Oct 15, 2001 at 09:35:58AM -0600, Warner Losh wrote: > In message <[EMAIL PROTECTED]> >"Peter van Heusden" writes: > : I noticed that PCI modems are detected in /sys/isa/sio.c. I added the > : chip > : id of the modem to the list of PCI devices (pci_ids), and now > : sio_pci_probe detects the modem, but the sioprobe() fails. Before I got > : digging into the sioprobe code (which seems rather complex), I'd like to > : verify that my pci_ids entry is correct. > : > : One thing I don't understand is the rid field of the pci_id structure. > : Some modems have this set to 0x10, others to 0x14. I'm not sure what to > : set it > : to - how do I determine this? > > look for the I/o space bar. this will be the the ones in the range > 0x10-0x24 that are odd (as in bit 0 is set). note, bars are 4 bytes > long (except for some 64 bit cards, but you can safely ignore that). > > Alternatively, > pciconf -r pciX:Y:Z 0x10:0x2f > and post it to the list. Thanks, Warner, but on further investigation, I discovered that the Duxbury modem is actually a re-branded Motorola SM56 - i.e. a WinModem. No wonder it doesn't work. Aaarrgh! I'm having a look at the Linux 2.4 kernel code, since they apparently have winmodem support (including for the SM56 chipset, which is now no longer supported by Motorola - double Aaaargh!), but will probably have to go with an external modem, since it seems to be impossible to get internal PCI non-winmodems. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Adding support for Duxbury PCI modem to FreeBSD 4.4
In message <[EMAIL PROTECTED]> "Peter van Heusden" writes: : I noticed that PCI modems are detected in /sys/isa/sio.c. I added the : chip : id of the modem to the list of PCI devices (pci_ids), and now : sio_pci_probe detects the modem, but the sioprobe() fails. Before I got : digging into the sioprobe code (which seems rather complex), I'd like to : verify that my pci_ids entry is correct. : : One thing I don't understand is the rid field of the pci_id structure. : Some modems have this set to 0x10, others to 0x14. I'm not sure what to : set it : to - how do I determine this? look for the I/o space bar. this will be the the ones in the range 0x10-0x24 that are odd (as in bit 0 is set). note, bars are 4 bytes long (except for some 64 bit cards, but you can safely ignore that). Alternatively, pciconf -r pciX:Y:Z 0x10:0x2f and post it to the list. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Adding support for Duxbury PCI modem to FreeBSD 4.4
Hi all I've just installed FreeBSD 4.4, and also recently purchased a \Duxbury 56kpci modem (a real modem, not a winmodem). I'm now trying to get this to work with 4.4, so... I noticed that PCI modems are detected in /sys/isa/sio.c. I added the chip id of the modem to the list of PCI devices (pci_ids), and now sio_pci_probe detects the modem, but the sioprobe() fails. Before I got digging into the sioprobe code (which seems rather complex), I'd like to verify that my pci_ids entry is correct. One thing I don't understand is the rid field of the pci_id structure. Some modems have this set to 0x10, others to 0x14. I'm not sure what to set it to - how do I determine this? Thanks for any help (btw. this is my first attempt to add anything to the FreeBSD kernel, so please excuse any naive questions). Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
