Paul ....
>>Bottom line: it's worth to detect HWUART, but fortunately it's as easy
>>as checking if /dev/ttyS3 exists and if not, falling back to /dev/ttyS1.
Both /dev/ttyS1 and /dev/ttyS3 existed in all the images that I have
played with. But only one of the gave positive response to :
/sbin/hciattach /dev/ttySX any 921600
Sometimes, depending on the image, it was 1 sometimes it was 3. There
was no possibility to check if only one of them exist....
> > 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.
>
I like brainstorming too..... I have one more coming to kernel-bugs in
few minutes ....
But getting back to the subject - as it goes for me - I can get used
to checking on what ttySx bluetooth shows up - but I guess blueprobe
is not that flexible.... I was about to provide a patch to OE but I
got lost ....
Shoul I/we think of better solution than blueprobe does :
module_id() {
awk 'BEGIN { FS=": " } /Hardware/ { print $2 } ' </proc/cpuinfo
}
and then assign the ttySx.
Should there be some extra code like for h2200 versions (Zeevo and CSR
)? Or should there be a command forcing the use of HWUART ?
Or maybe should I forget about the whole BT stuff for now and
concentrate on more important things .... ?
Cheers
Michal Panczyk
Received on Mon Feb 18 2008 - 17:55:34 EST
This archive was generated by hypermail 2.2.0 : Mon Feb 18 2008 - 17:55:48 EST