Re: Opie bluetooth applet.

Dnia czwartek, 22 czerwca 2006 14:22, Dmitriy Korovkin napisał:
> Erik Hovland wrote:
> >On Wed, Jun 21, 2006 at 10:55:33PM +0400, Dmitriy Korovkin wrote:

> >>1. Why text file - not configuration file?
> >The h2200 handheld can ship with 2 different bt chips. One requires one
> >type of config, one requires another.
> >Slavek submitted a previous patch which determined the bt chip type by
> >directly reading the MTD device.
> >That was unsatisfactory for familiar distros. So I asked Slavek to
> >submit a patch which read a common text file instead.

> I don't see a rason why.

1. to not repeat code
2. to get device related code out of OPIE
3. to be able to add new PDA with BT module working without having to 
patch/compile OPIE

> >>2. What to do with this file? How the user will configure it?
> >Hopefully the distro will populate it (familiar does).
> >If you know of another way to figure out this info, let me and Slavek
> >know.

> Yes, I know, I've implemented this in the Bluetooth Manager.

Machine will get it configured anyway in base system - I think that we do 
not have to repeat what was already done. 

> >If it is unsatisfactory, please propose other options.

> What I currently see in BT system - a lot of "patch and fix". Bt obex
> that doesn't seem to receive, Manager that did (now it does something)
> nothing.

Then leave device related stuff such like detecting which BT module h2200 
has and work on getting BT working better in OPIE?

-- 
JID: hrw-jabber.org
Sharp Zaurus C-760 (OZ 3.5.x)
OpenEmbedded/OpenZaurus/OPIE developer

             Today is the first day of the rest of your life.
_______________________________________________

http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex

Opie-devel mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie-devel