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

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....

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.

Michal

[1]: http://projects.linuxtogo.org/pipermail/openembedded-commits/2007-January/002931.html

On Feb 18, 2008 7:49 PM, Erik Hovland <erik_at_hovland.org> wrote:
> On Mon, Feb 18, 2008 at 08:26:55PM +0200, Paul Sokolovsky wrote:
> > I personally don't have clear picture how HWUART is better BTUART.
> > IIRC, HWUART allows for higher speed range, but even BTUART should be
> > able to do 900K. So, finding 10mins to read PXA manual may be
> > beneficial here (and the whole matter of figuring this out should be big
> > fun ;-) ).
>
> The bluetooth device in the h5xxx iPAQs is basically flawed. So
> using the HWUART is not a complete solution to the problems found there.
> But empirical evidence provided by past developers shows that the
> hardware flow control provided by HWUART does improve the stability of
> bluetooth usage.
>
> So if the HWUART can be used, it should be. And since it is physically
> wired to the same pins, there is little impact to the user.
>
> Since this is still work in progress, I have no problem with accepting
> it and making BTUART the default. But at some time the issue of
> bluetooth stability will come up and it will have to addressed.
>
>
> E
>
> --
> Erik Hovland
> mail: erik_at_hovland.org
> web: http://hovland.org/
> PGP/GPG public key available on request
>
> _______________________________________________
> H5400-port mailing list
> H5400-port_at_handhelds.org
> https://www.handhelds.org/mailman/listinfo/h5400-port
>

-- 
Michal