[Bluez-users] Philips PC Card + 2.6.10 kernel.

[Bluez-users] Philips PC Card + 2.6.10 kernel.

[Peter Johanson]

(Resent, as it was sent from the wrong address the first time)
Hey all,

I'm working on getting a newly aquired Philips PC Card working, using a
2.6.10 kernel (-gentoo-r4 to be specific). I believe i've run into the
problem as described here (and as potentially fixed for some -mmX sources):
http://sourceforge.net/mailarchive/message.php?msg_id=9953048,
which claimed to be resolved for 2.6.10-rc1-mm2, which I also gave a
try, but was unable to actually test, as my keyboard refused to work
with that kernel. I've also tried 2.6.10-mm2, with the same failure.
Here's the info on the card:

lspci -vvv for the card:
0000:03:00.0 Serial controller: Oxford Semiconductor Ltd OXCB950 Cardbus 16950 UART (prog-if 06 [16950])
	Subsystem: Oxford Semiconductor Ltd: Unknown device 0001
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at 4010
	Region 1: Memory at 40800000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at 4000 [size=16]
	Region 3: Memory at 40801000 (32-bit, non-prefetchable) [size=4K]
	Region 4: Memory at 40802000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <available only to root>

dmesg, after implementing the small patch discussed here to recognize the card
http://www.cs.helsinki.fi/linux/linux-kernel/2002-08/1374.html:

PCI: Enabling device 0000:03:00.0 (0000 -> 0003)
ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 11 (level, low) -> IRQ 11
ttyS14: detected caps 00000700 should be 00000100
ttyS14 at I/O 0x4010 (irq = 11) is a 16C950/954

Having found the specs based on the FCC ID on the FCC site, i know this
is the OXford Semiconductor chipset with a BlueCore01 inside. As such, I
tried:
gonzo root # hciattach /dev/ttyS14 bcsp 921600
BCSP initialization timed out

Was there ever any success in finding out what had changed for the user
who reported success for 2.6.10-r1-mm2? Any suggestions on ways to debug
this? Thanks in advance.

-pete

-- 
Peter Johanson
<latexer@gentoo.org>


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Philips PC Card + 2.6.10 kernel.

[Marcel Holtmann]

Hi Peter,

> (Resent, as it was sent from the wrong address the first time)
> Hey all,

look for the answer in the previous thread, because I am not going to
repost it.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

[Bluez-users] Philips PC Card + 2.6.10 kernel.

[Peter Johanson]

Hey all,

I'm working on getting a newly aquired Philips PC Card working, using a
2.6.10 kernel (-gentoo-r4 to be specific). I believe i've run into the
problem as described here (and as potentially fixed for some -mmX sources):
http://sourceforge.net/mailarchive/message.php?msg_id=9953048,
which claimed to be resolved for 2.6.10-rc1-mm2, which I also gave a
try, but was unable to actually test, as my keyboard refused to work
with that kernel. I've also tried 2.6.10-mm2, with the same failure.
Here's the info on the card:

lspci -vvv for the card:
0000:03:00.0 Serial controller: Oxford Semiconductor Ltd OXCB950 Cardbus 16950 UART (prog-if 06 [16950])
	Subsystem: Oxford Semiconductor Ltd: Unknown device 0001
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at 4010
	Region 1: Memory at 40800000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at 4000 [size=16]
	Region 3: Memory at 40801000 (32-bit, non-prefetchable) [size=4K]
	Region 4: Memory at 40802000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <available only to root>

dmesg, after implementing the small patch discussed here to recognize the card
http://www.cs.helsinki.fi/linux/linux-kernel/2002-08/1374.html:

PCI: Enabling device 0000:03:00.0 (0000 -> 0003)
ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 11 (level, low) -> IRQ 11
ttyS14: detected caps 00000700 should be 00000100
ttyS14 at I/O 0x4010 (irq = 11) is a 16C950/954

Having found the specs based on the FCC ID on the FCC site, i know this
is the OXford Semiconductor chipset with a BlueCore01 inside. As such, I
tried:
gonzo root # hciattach /dev/ttyS14 bcsp 921600
BCSP initialization timed out

Was there ever any success in finding out what had changed for the user
who reported success for 2.6.10-r1-mm2? Any suggestions on ways to debug
this? Thanks in advance.

-pete

-- 
Peter Johanson
<latexer@gentoo.org>


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Philips PC Card + 2.6.10 kernel.

[Marcel Holtmann]

Hi Peter,

> I'm working on getting a newly aquired Philips PC Card working, using a
> 2.6.10 kernel (-gentoo-r4 to be specific). I believe i've run into the
> problem as described here (and as potentially fixed for some -mmX sources):
> http://sourceforge.net/mailarchive/message.php?msg_id=9953048,
> which claimed to be resolved for 2.6.10-rc1-mm2, which I also gave a
> try, but was unable to actually test, as my keyboard refused to work
> with that kernel. I've also tried 2.6.10-mm2, with the same failure.

that thread is different and actually the change I mentioned there came
in around 2.6.9 and was for serial_cs only.

> Here's the info on the card:
> 
> lspci -vvv for the card:
> 0000:03:00.0 Serial controller: Oxford Semiconductor Ltd OXCB950 Cardbus 16950 UART (prog-if 06 [16950])
> 	Subsystem: Oxford Semiconductor Ltd: Unknown device 0001
> 	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> 	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> 	Interrupt: pin A routed to IRQ 11
> 	Region 0: I/O ports at 4010
> 	Region 1: Memory at 40800000 (32-bit, non-prefetchable) [size=4K]
> 	Region 2: I/O ports at 4000 [size=16]
> 	Region 3: Memory at 40801000 (32-bit, non-prefetchable) [size=4K]
> 	Region 4: Memory at 40802000 (32-bit, non-prefetchable) [size=4K]
> 	Capabilities: <available only to root>

So this is a CardBus card and not a PCMCIA card. These cards are very
rare and I don't have one of these. The Socket card is still an old ISA
PCMCIA card.

> dmesg, after implementing the small patch discussed here to recognize the card
> http://www.cs.helsinki.fi/linux/linux-kernel/2002-08/1374.html:
> 
> PCI: Enabling device 0000:03:00.0 (0000 -> 0003)
> ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 11 (level, low) -> IRQ 11
> ttyS14: detected caps 00000700 should be 00000100
> ttyS14 at I/O 0x4010 (irq = 11) is a 16C950/954
> 
> Having found the specs based on the FCC ID on the FCC site, i know this
> is the OXford Semiconductor chipset with a BlueCore01 inside. As such, I
> tried:
> gonzo root # hciattach /dev/ttyS14 bcsp 921600
> BCSP initialization timed out

It can also work in H4 mode and then you need to use "csr" or your baud
rate is wrong. The hciattach tool gives you a lot of parameters and you
should try some of them.

> Was there ever any success in finding out what had changed for the user
> who reported success for 2.6.10-r1-mm2? Any suggestions on ways to debug
> this? Thanks in advance.

Since Fabrizio works for Philips, you might wanna contact him and don't
forget to put me on CC. It seems that the current kernel is still
missing some patches. And btw feel free to donate one of these cards to
me for testing.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Philips PC Card + 2.6.10 kernel.

[Peter Johanson]

On Fri, Jan 14, 2005 at 08:47:17AM +0100, Marcel Holtmann wrote:
<snip/>
> > dmesg, after implementing the small patch discussed here to recognize the card
> > http://www.cs.helsinki.fi/linux/linux-kernel/2002-08/1374.html:
> > 
> > PCI: Enabling device 0000:03:00.0 (0000 -> 0003)
> > ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 11 (level, low) -> IRQ 11
> > ttyS14: detected caps 00000700 should be 00000100
> > ttyS14 at I/O 0x4010 (irq = 11) is a 16C950/954
> > 
> > Having found the specs based on the FCC ID on the FCC site, i know this
> > is the OXford Semiconductor chipset with a BlueCore01 inside. As such, I
> > tried:
> > gonzo root # hciattach /dev/ttyS14 bcsp 921600
> > BCSP initialization timed out
> 
> It can also work in H4 mode and then you need to use "csr" or your baud
> rate is wrong. The hciattach tool gives you a lot of parameters and you
> should try some of them.

I've tried both csr and bcsp at all the available baud rates listed in
the man page, with the same results. The only other options available
seem to be either the initialization timeout, or flow/noflow. Should i
try the various permutations involving flow/noflow as well?

> 
> > Was there ever any success in finding out what had changed for the user
> > who reported success for 2.6.10-r1-mm2? Any suggestions on ways to debug
> > this? Thanks in advance.
> 
> Since Fabrizio works for Philips, you might wanna contact him and don't
> forget to put me on CC. It seems that the current kernel is still
> missing some patches. And btw feel free to donate one of these cards to
> me for testing.
> 

I'll try contacting him, thanks. I only have one of these cards, so a
permanent donation isn't really an option for me, but if a temporary
loan would help, I'd be more than willing to if none of my poking
results in a working card for me.

Thanks,

-pete

> Regards
> 
> Marcel
> 
> 

-- 
Peter Johanson
<latexer@gentoo.org>


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users