Re: Re: [Kernel-bugs] h5400 patch - merge h5400_bt.c back to h5400.c

Hello,

On Mon, 18 Feb 2008 20:17:46 +0100
"Michal Panczyk" <mpanczyk_at_gmail.com> wrote:

> Thanks guys for help - I am glad it got committed. I will probably
> need some more help with rest of the stuff - but that's a story for a
> different mail...
>
> Paul:
> To be honest - I don't really understand all this situation with
> ttys.... During my "adventures" with different angstrom images
> (different releases....) I found that bluetooth tty changes from image
> to image - sometimes it is available at 1, sometimes at 3. I didn't
> really pay attention to the reason of that changes.... Yes - it was on
> the same device....

Well, it's simple - ttyS numbers are dictated by hardware (PXA), not by
distro:

ttyS0 is FFUART, on classical PDA it's full serial port with pins on
cradle connector
ttyS1 is BTUART, supposedly attached to BT chip if it is there
ttyS2 is STUART, used for IrDA
ttyS3 is PXA255+, uses the same chip pins as BTUART (well, it can use
PCMCIA pins too, but obviously linux doesn't use that mode).

Note "classical PDA" above - new devices like with phones and GPSes may
have such modules there.

>
> ttyS3 was introduced to OE by Koen [1]- but I guess he had exactly the
> same knowledge about the reason of the change - it probably worked for
> him in this configuration... Earlier it used to work at ttys/1
> (Familiar was using this layout - I remember from h2200 port). I
> remember for Familiar that h5400 devices and h3900 were pretty the
> same - before the change both used "1".
>
> Summarizing - I hope it is not going to change again. If there is
> going be such a situation - I will take a closer look at that.
>
> Erik :
> I added HWUART and BTUART to my TODO, after I finish things with
> h5000.c.

As you see in another message, starting to think about the stuff
together is the best incentive to brainstorm the issue ;-). So, we
should use ttyS3 when it is available.

>
> Michal
>

[]

-- 
Best regards,
 Paul                          mailto:pmiscml_at_gmail.com