Re: [Soekris] Net6501, 2nd serial and Linux 3.1

2012-02-13 Thread Philippe Vanhaesendonck
On Sun, 12 Feb 2012 17:22:51 -0800, Peter Neubauer
 wrote:

> Somewhat related, is the internal port at "RS-232" voltage levels, or is
> it a TTL/LVTTL level port?

It is the real thing ;)
I use it communicate with my UPS.

-- 
Philippe
___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech


Re: [Soekris] Net6501, 2nd serial and Linux 3.1

2012-02-12 Thread Peter Neubauer
> Did you have any "real" success? (I mean physically connecting the 2nd 
> serial?)

Unfortunately, no.  I don't have anything connected to the second serial port 
yet.

Somewhat related, is the internal port at "RS-232" voltage levels, or is it a 
TTL/LVTTL level port?
___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech


Re: [Soekris] Net6501, 2nd serial and Linux 3.1

2012-02-12 Thread Philippe Vanhaesendonck
On 12/02/12 22:38, Peter Neubauer wrote:
> On my Linux 3.2.1 system, the kernel recognizes the additional serial devices 
> using the "pch_uart" driver.  It looks like 3.1 has the same driver.  I 
> recommend confirming that you have the pch_uart module (if not, you may have 
> to build it from kernel source) and then try "modprobe pch_uart".
>   -Peter
>

Thanks for your answer.

In the meantime we have 3.2.0 arrived in Debian wheezy, so I tried 
again, and got exactly the same problem.

I realized as well that they are handled by the "pch_uart" driver, I can 
modprobe, the driver "see" the devices and creates the associated 
/dev/ttyPCHn, but it just does not work :(

Did you have any "real" success? (I mean physically connecting the 2nd 
serial?)

I then traced the changes in the sources and decided to comment out the 
pci ids definitions in 8250_pci.c so that they aren't handled by 
"pch_uart" as they were not in the past...

... and now they are recognized again as ttySn, and it works perfectly :)

Still need to figure out how to get the same result without recompiling 
a kernel, as I would prefer to stay on Debian stock kernel...

-- 
Philippe
___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech


Re: [Soekris] Net6501, 2nd serial and Linux 3.1

2012-02-12 Thread Peter Neubauer
On my Linux 3.2.1 system, the kernel recognizes the additional serial devices 
using the "pch_uart" driver.  It looks like 3.1 has the same driver.  I 
recommend confirming that you have the pch_uart module (if not, you may have to 
build it from kernel source) and then try "modprobe pch_uart".
-Peter

On Feb 11, 2012, at 12:26 PM, Philippe Vanhaesendonck wrote:

> Hello everybody!
> 
> Does anybody have any luck with the 2nd serial on the net6501 under 
> Linux 3.1?
> 
> With Linux 2.6.X the dmesg show (copied from Wim):
> 
>> [1.793175] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> [1.793401] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a TI16750
>> [1.794537] :02:0a.1: ttyS1 at I/O 0x1020 (irq = 9) is a 16550A
>> [1.795004] :02:0a.2: ttyS2 at I/O 0x1028 (irq = 9) is a 16550A
>> [1.795203] serial :02:0a.3: enabling device ( -> 0003)
>> [1.795231] serial :02:0a.3: can't find IRQ for PCI INT B;
> please try using pci=biosirq
> 
> 
> But under 3.1 it looks like ttyS1 is not recognized, I have:
> 
>> [2.100734] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> [2.100734] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a TI16750
>> [2.148602] pci :01:00.0: using bridge :00:17.0 INT D to
> get IRQ 19
>> [2.148623] serial :02:0a.1: PCI->APIC IRQ transform: INT D ->
> IRQ 19
>> [2.148801] pci :01:00.0: using bridge :00:17.0 INT D to
> get IRQ 19
>> [2.148819] serial :02:0a.2: PCI->APIC IRQ transform: INT D ->
> IRQ 19
>> [2.148986] pci :01:00.0: using bridge :00:17.0 INT D to
> get IRQ 19
>> [2.149003] serial :02:0a.3: PCI->APIC IRQ transform: INT D ->
> IRQ 19
>> [2.149167] pci :01:00.0: using bridge :00:17.0 INT D to
> get IRQ 19
>> [2.149184] serial :02:0a.4: PCI->APIC IRQ transform: INT D ->
> IRQ 19
> 
> Any idea?
> 
> --
> Philippe
> 
> -- 
> Philippe
> ___
> Soekris-tech mailing list
> Soekris-tech@lists.soekris.com
> http://lists.soekris.com/mailman/listinfo/soekris-tech
> 

___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech


[Soekris] Net6501, 2nd serial and Linux 3.1

2012-02-11 Thread Philippe Vanhaesendonck
Hello everybody!

Does anybody have any luck with the 2nd serial on the net6501 under 
Linux 3.1?

With Linux 2.6.X the dmesg show (copied from Wim):

> [1.793175] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> [1.793401] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a TI16750
> [1.794537] :02:0a.1: ttyS1 at I/O 0x1020 (irq = 9) is a 16550A
> [1.795004] :02:0a.2: ttyS2 at I/O 0x1028 (irq = 9) is a 16550A
> [1.795203] serial :02:0a.3: enabling device ( -> 0003)
> [1.795231] serial :02:0a.3: can't find IRQ for PCI INT B;
please try using pci=biosirq


But under 3.1 it looks like ttyS1 is not recognized, I have:

> [2.100734] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> [2.100734] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a TI16750
> [2.148602] pci :01:00.0: using bridge :00:17.0 INT D to
get IRQ 19
> [2.148623] serial :02:0a.1: PCI->APIC IRQ transform: INT D ->
IRQ 19
> [2.148801] pci :01:00.0: using bridge :00:17.0 INT D to
get IRQ 19
> [2.148819] serial :02:0a.2: PCI->APIC IRQ transform: INT D ->
IRQ 19
> [2.148986] pci :01:00.0: using bridge :00:17.0 INT D to
get IRQ 19
> [2.149003] serial :02:0a.3: PCI->APIC IRQ transform: INT D ->
IRQ 19
> [2.149167] pci :01:00.0: using bridge :00:17.0 INT D to
get IRQ 19
> [2.149184] serial :02:0a.4: PCI->APIC IRQ transform: INT D ->
IRQ 19

Any idea?

--
Philippe

-- 
Philippe
___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech