You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(4) |
Nov
(8) |
Dec
(27) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(23) |
Feb
(28) |
Mar
(39) |
Apr
(79) |
May
(17) |
Jun
(1) |
Jul
(8) |
Aug
(11) |
Sep
(27) |
Oct
(12) |
Nov
(2) |
Dec
(24) |
2004 |
Jan
(15) |
Feb
(51) |
Mar
(80) |
Apr
(34) |
May
(19) |
Jun
(45) |
Jul
(8) |
Aug
(35) |
Sep
(17) |
Oct
(49) |
Nov
(98) |
Dec
(53) |
2005 |
Jan
(54) |
Feb
(93) |
Mar
(87) |
Apr
(102) |
May
(27) |
Jun
(30) |
Jul
(11) |
Aug
(39) |
Sep
(22) |
Oct
(28) |
Nov
(13) |
Dec
(20) |
2006 |
Jan
(14) |
Feb
(201) |
Mar
(101) |
Apr
(138) |
May
(149) |
Jun
(43) |
Jul
(42) |
Aug
(97) |
Sep
(42) |
Oct
(69) |
Nov
(12) |
Dec
(20) |
2007 |
Jan
(32) |
Feb
(15) |
Mar
(27) |
Apr
(63) |
May
(15) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Marcin J. <ope...@hr...> - 2007-04-20 14:22:47
|
Currently OpenEmbedded is used to build =C5ngstr=F6m images and they are=20 provided to testers from time to time in console and x11 flavours. Few=20 developers works on getting OPIE support in this distro. Thx to Thomas Kunze we have first versions of SD/MMC driver for Collie so=20 it looks like 2.6 kernel will be sooner or later usable for users. Some=20 things are still lacking but maybe someone will work on getting them=20 resolved. Other Zaurus models works OK under 2.6.20 kernel (Tosa req 2.6.17 due to=20 USB Host changes in newer kernels) so they are ready to switch. Why I am writing this? Currently I have many projects on my head and lack=20 time for work on OpenZaurus full release (it took me two months of work=20 last year). We have small developer base so I do not want to maintain=20 release which will be like =C5ngstr=F6m but compiled with other options. So we have to choose: 1. we release OpenZaurus 3.5.5 for all Zaurus models 2. we release OpenZaurus 3.5.5 for Collie/2.4 only 3. we close OpenZaurus history and switch to =C5ngstr=F6m =46irst option require few developers with OE knowledge, atleast one=20 developer with device for making tests and someone who will maintain test=20 phase (handling mails from hundred users which boot test images). Second option means less work - only one machine, less testers needed. Third option means work too. Please vote - I want to know what you OpenZaurus developers think about=20 it. This is our distribution so we have to decide what to do with it. =2D-=20 JID: hrw-jabber.org OpenEmbedded developer/consultant there are actually only 10 web sites out there, all the others are rearranged copies |
From: Marcin J. <ope...@hr...> - 2007-04-19 21:42:03
|
Dnia czwartek, 19 kwietnia 2007, Scott Bronson napisa=B3: > I'm not sure what's going on... at a glance, it looks like Berlios is > having NFS issues. Wish I could have been faster at moving the OZ wiki > to linuxtogo.org. On LTG /var/www/openzaurus/wiki/ contain wiki and ozdump fetched today=20 from SVN. Register at http://projects.linuxtogo.org/projects/openzaurus/=20 so you will get access to it. > hrw, could you add a link on the OZ blog to the read-only mirror on > http://ozwiki.u32.net ? Hopefully that will tide people over until I > can fix this for good. I sent you details of you account to Wordpress used on OZ website. Login=20 and change it by yourself ;) > If Berlios doesn't come back in a few days, I'll see if I can free up > some time to make the linuxtogo move. Thx. openzaurus.org/wiki/ will be OK for start and then we will pester=20 Kergoth to move wiki.openzaurus.org CNAME to LTG. =2D-=20 JID: hrw-jabber.org OpenEmbedded developer/consultant Real programmers don't document. If it was hard to write, it should be hard to understand. |
From: Scott B. <br...@ri...> - 2007-04-19 18:07:33
|
I'm not sure what's going on... at a glance, it looks like Berlios is having NFS issues. Wish I could have been faster at moving the OZ wiki to linuxtogo.org. hrw, could you add a link on the OZ blog to the read-only mirror on http://ozwiki.u32.net ? Hopefully that will tide people over until I can fix this for good. If Berlios doesn't come back in a few days, I'll see if I can free up some time to make the linuxtogo move. - Scott |
From: Marcin J. <ope...@hr...> - 2007-04-18 13:33:38
|
Dnia =B6roda, 18 kwietnia 2007, Arieh Skliarouk napisa=B3: > I know, this is mailing list for openzaurus distro, but since the only > distro that was built for collie with kernel 2.6 is Angstrom, this is > what I am going to check. OpenZaurus-devel ML is also used for Zaurus development nevermind which=20 distro is used (as long as it is OZ or OE derived). > My first question is, why modules (file modules-2.6.20.6-collie.tgz) > were supplied separately, and not as part of rootfs image? > The image has 6+ MB of free space, more than enough to host all the > modules.=20 modules-KERNEL_VER-MACHINE.tgz contain ALL modules for machine. By default= =20 images generated by OpenEmbedded contain only needed modules. We can=20 change it for collie/2.6 anyway as this is rather test device. > If the goal was to avoid rootfs bloat with unnecessary modules, then > the rootfs should at least include following critical modules: > > 2.6.20.6/kernel/drivers/ide/ide-core.ko // To mount the CF cards > 2.6.20.6/kernel/drivers/net/wireless/hostap/hostap.ko // For the WiFi > > 2.6.20.6/kernel/drivers/spi/locomo_spi.ko // For the SD > 2.6.20.6/kernel/drivers/mmc/mmc_block.ko > > Could be there are other modules that must be on rootfs. ok =2D-=20 JID: hrw-jabber.org OpenEmbedded developer/consultant Packrat's Credo: I have no use for it, but I hate to see it go to waste. |
From: Arieh S. <skl...@gm...> - 2007-04-18 11:29:36
|
Hi, I know, this is mailing list for openzaurus distro, but since the only distro that was built for collie with kernel 2.6 is Angstrom, this is what I am going to check. Yesterday, Marcin Juszkiewicz posted about Angstrom images for collie with 2.6 kernel, done by Koen Kooi: http://blog.haerwu.biz/2007/04/17/collie-and-sdmmc-support-under-26-kernel/ My first question is, why modules (file modules-2.6.20.6-collie.tgz<http://www.angstrom-distribution.org/unstable/images/collie/20070417/modules-2.6.20.6-collie.tgz>) were supplied separately, and not as part of rootfs image? The image has 6+ MB of free space, more than enough to host all the modules. If the goal was to avoid rootfs bloat with unnecessary modules, then the rootfs should at least include following critical modules: 2.6.20.6/kernel/drivers/ide/ide-core.ko // To mount the CF cards 2.6.20.6/kernel/drivers/net/wireless/hostap/hostap.ko // For the WiFi 2.6.20.6/kernel/drivers/spi/locomo_spi.ko // For the SD 2.6.20.6/kernel/drivers/mmc/mmc_block.ko Could be there are other modules that must be on rootfs. -- Arieh |
From: Arieh S. <skl...@gm...> - 2007-04-18 04:45:33
|
Hi, I don't know about the 4GB ST1's, but on the 5GB iPod drives, only firmware > version 3.03 or less works. 3.04 and above have some sort of > "protection" that makes them useless outside of an MP3 player. Mine is working properly, when inserted into an CF-USB adapter. -- Arieh |
From: Henry v. T. <hvo...@sb...> - 2007-04-17 22:01:59
|
Arieh Skliarouk wrote: > Today I tried to test an 4GB CF Seagate ST1 harddisk (ripped from an > broken iPod). The disk produced the same error messages on 2.6, as on 2.4: > > <5>pccard: PCMCIA card inserted into slot 0 > <5>pcmcia: registering new device pcmcia0.0 > <6>Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > <6>ide: Assuming 50MHz system bus speed for PIO modes; override with > idebus=xx > <7>Probing IDE interface ide0... > ... > <5>ide-cs: ide_register() at 0xc4820000 & 0xc482000e, irq 35 failed > <7>Probing IDE interface ide0... > ... > <5>ide-cs: ide_register() at 0xc4820000 & 0xc482000e, irq 35 failed > <5>pccard: card ejected from slot 0 > > May be you have a clue on this?... I don't know about the 4GB ST1's, but on the 5GB ones, only firmware version 3.03 or less works. 3.04 and above have some sort of "protection" that makes them useless outside of an MP3 player. |
From: Arieh S. <skl...@gm...> - 2007-04-17 09:31:57
|
Hello Thomas, > * Battery LED remains off on power connect. Apparently, the > > battery is actually charged, as the thing is working for an hour > > already with WiFI on. > > > The kernel should not charge the battery. If you have the power cable > connected, the zaurus don't need a battery. I think that kernel needs to turn on the yellow "charging battery" LED on AC power plug-in, and turn off the LED, on AC power disconnection (Like the 2.4kernel did). Today I tried to test an 4GB CF Seagate ST1 harddisk (ripped from an broken iPod). The disk produced the same error messages on 2.6, as on 2.4: <5>pccard: PCMCIA card inserted into slot 0 <5>pcmcia: registering new device pcmcia0.0 <6>Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 <6>ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx <7>Probing IDE interface ide0... ... <5>ide-cs: ide_register() at 0xc4820000 & 0xc482000e, irq 35 failed <7>Probing IDE interface ide0... ... <5>ide-cs: ide_register() at 0xc4820000 & 0xc482000e, irq 35 failed <5>pccard: card ejected from slot 0 May be you have a clue on this?... Apparently the Collie SD drive does not support MMC+ standard, as the kernel did not reported anything in dmesg, when I inserted an MMC+ 128MB card. Am I right? -- Arieh |
From: Thomas K. <tho...@gm...> - 2007-04-15 11:51:09
|
Hi, I'm glad, that the driver works for you ;) Arieh Skliarouk wrote: > There were following messages in dmesg: > > <7>Collie MMC over SPI Driver > <6>mmc_spi .0: SD/MMC <-> SPI proxy driver, no card power management > <4>mmc0: Problem switching card into high-speed mode! > <6>mmcblk0: mmc0:0000 SD01G 992000KiB > <6> mmcblk0: unknown partition table So your card does'nt have a partition table. > <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended > > I was able to see files on it. md5sum of /dev/mmcblk0 returned same > result twice. > Data reading speed was about 735 kb/s (readed 1GB in 1381 seconds). > > Write was faster, at about 1028kb/s. I used following commands to test > write speed: > > date; dd if=/dev/zero of=writetest bs=1024k count=100; sync; date AFAIK hdparm -t of -T is much better to test performance. > I don't know whether following issues are user-space or kernel-space: > > * Battery LED remains off on power connect. Apparently, the > battery is actually charged, as the thing is working for an hour > already with WiFI on. > The kernel should not charge the battery. If you have the power cable connected, the zaurus don't need a battery. > > * USB-net interface is not activated. May be I miss a kernel module? > This is not implemented yet. > > * Keyboard mapping of "OK" button is not "ENTER". > This is an userspace problem. You can change the keymap in /etc/keymap-2.6.map and reload it with loadkeys. >frame-buffers is turned off completely after several minutes of inactivity on the console. IMHO, unless configured, the default >behavior should be just to turn off highlighting. This should be a userspace problem. Try killing apmd. > > * When I press "Cancel" button, I get following error: "power.c > device-level power management is not supported yet.". Do you > plan to work on it? > * State of "battery compartment switch" is disregarded, as the > device starts booting immediately as I press "RESET" button. > * Apparently, /dev/sharp_buz is not implemented yet. I tried to > check it using attached "buzzme" (taken from kismet) program. > * command "halt" did not led power down, but rather to some > suspended state, with garbage on FB (with console output > remnants). After I closed the keyboard compartment, the system > started regular booting. > This are kernel issues. > I remember, that from-factory Sharp Zaurus distro was able to utilize > built-in speaker, to playback music. Will it be possible with the > kernel 2.6? Why was the peripheral abandoned in OpenZaurus? AFAIK. The alarms weren't working. And as nobody wanted to look into the ugly embedix code ... I think the feature will be implemented at some future time. Cheers, Thomas |
From: Justin P. <pap...@gm...> - 2007-04-15 05:41:40
|
On 1/25/07, Justin Patrin <pap...@gm...> wrote: > > http://oe.reversefold.com/sharpsl-rc/sharpsl-rc-2.6.18-r0.patch > > A patch for kernel 2.6.18. This works just fine but I had to comment > out the spitzkbd.c use of AK_INT as it didn't want ot share the IRQ > with sharpsl-rc. > I updated the driver to work with 2.6.20 a while ago in OE but have now updated it to compile for the c7x0/corgi. It should be available here when the website updates: http://www.openembedded.org/repo/org.openembedded.dev/packages/linux/linux-rp-2.6.20/sharpsl-rc-r1.patch or from the OE mtn repo. If anyone has a CE-RH1 remote and a cxx0 Zaurus I'd appreciate some help getting the correct key codes from that machine as I know they're different. -- Justin Patrin |
From: Marcin J. <ope...@hr...> - 2007-04-13 10:23:49
|
My tests with: - 16MB MMC (Canon) - 64MB SD (Sandisk) - 64MB RS-MMC (Noname added to Nokia770) - 512MB SD (Kingston) Insert of 16MB MMC: <6>mmcblk0: mmc0:0001 16M 15680KiB <6> mmcblk0: p1 <3>FAT: invalid media value (0x01) <6>VFS: Can't find a valid FAT filesystem on dev mmcblk0. <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended Card was automounted, "md5sum /dev/mmcblk0" return same result for 3 runs. Ejected, inserted 64MB SD: <3>mmc_spi .0: can't initialize the card: no card? <3>mmc_spi .0: CMD55 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: CMD55 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: CMD55 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: CMD55 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: CMD1 response SPI_R1: INVALID RESPONSE, 80 64MB RS-MMC was not at all recognized - no reaction other then: <3>mmc_spi .0: can't initialize the card: no card? 512MB SD: <3>mmc_spi .0: CMD0 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: CMD0 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: can't initialize the card: no card? <3>mmc_spi .0: CMD55 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: CMD55 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: CMD55 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: CMD55 response SPI_R1: INVALID RESPONSE, 80 <3>mmc_spi .0: CMD1 response SPI_R1: INVALID RESPONSE, 80 -- JID: hrw-jabber.org OpenEmbedded developer/consultant 42? 7 and a half million years and all you can come up with is 42?! |
From: Thomas K. <tho...@gm...> - 2007-04-12 23:48:30
|
Hello, I put an angstrom bootstrap image at www2.informatik.hu-berlin.de/~tkunze/zaurus/images . You have to modprobe the modules locomo_spi and mmc_block. If you get the message: mmc0: error requesting CID: 4 after you removed a card, its normal behavior: The mmc-layer doen't get a response from a card. If your card doesn't work, try reinserting it. I attached a "mtn diff" to linux-rp. Cheers, Thomas |
From: Arieh S. <skl...@gm...> - 2007-04-11 12:20:18
|
Hello Thomas, On 4/11/07, Thomas Kunze <tho...@gm...> wrote: > > Arieh Skliarouk wrote: > > > > > > I see directory > > http://www2.informatik.hu-berlin.de/~tkunze/zaurus/images/ > > <http://www2.informatik.hu-berlin.de/%7Etkunze/zaurus/images/> > > > > Are these files kernel 2.6 for collie with the aforementioned patches, > > along with bootable rootfs? > > > > Can I rename the rootfs to initrd.bin prior to reflash?- > Well yes. But its an old version. The kernel doesn't include the > bootmessages fix, the kexec fix, and the MMC Cards run at lowest speed. > But it should work as a proof of concept. > > I can provide new Images when I get OE working again. > If it is matter of several days, I would rather wait. Thank you for the work! -- Arieh |
From: Marcin J. <ope...@hr...> - 2007-04-11 06:35:49
|
Dnia wtorek, 10 kwietnia 2007, Thomas Kunze napisa=C5=82: > Hi, > > I wrote a SPI Driver for Collie. All my SD Cards work on Collie now. > > Patches can be found at > http://www2.informatik.hu-berlin.de/~tkunze/zaurus/patches . > I would appreciate comments and suggestions. Please share your recipe and defconfig - my kernel has problems with=20 booting. Do you know that users created bounty for getting SD/MMC support for=20 collie? Currently it is over 300 USD (paid when driver hit mainline=20 kernel). I want also note that when this will work OK for users collie will join=20 list of =C3=85ngstr=C3=B6m supported machines ;) BIG Thx for working on this driver Thomas! =2D-=20 JID: hrw-jabber.org OpenEmbedded developer/consultant punk's not dead. it just smells that way. |
From: Arieh S. <skl...@gm...> - 2007-04-11 05:53:54
|
Hello, > I wrote a SPI Driver for Collie. All my SD Cards work on Collie now. Very good news! Big thank you! I have waited for the kernel 2.6 on collie for a long time already. > Patches can be found at > > http://www2.informatik.hu-berlin.de/~tkunze/zaurus/patches . I see directory http://www2.informatik.hu-berlin.de/~tkunze/zaurus/images/ Are these files kernel 2.6 for collie with the aforementioned patches, along with bootable rootfs? Can I rename the rootfs to initrd.bin prior to reflash? -- Arieh |
From: Anthony J. S. <ant...@ie...> - 2007-04-10 19:42:45
|
How do I test this? Have you submitted it to the kernel mailing list for inclusion in the mainline kernel? Tony On Tue, 2007-04-10 at 20:05 +0200, Thomas Kunze wrote: > Hi, > > I wrote a SPI Driver for Collie. All my SD Cards work on Collie now. > > Patches can be found at > http://www2.informatik.hu-berlin.de/~tkunze/zaurus/patches . > > The important ones for mmc are: > locomo-r0.patch: > -fixes GPIO direction setting > -implements SPI irq setting > locomo_spi-r2.patch > -the spi driver > mmc_spi-r2.patch > -from LKML with very little changes by me > > The other patches worth noting: > collie-kexec.patch > - fix kexec for collie > collie-r3.patch > - refreshed patch from OE > - fix boottime serial console output > > All other patches are refreshed versions of the patches in OE. > > I would appreciate comments and suggestions. > Cheers, > > Thomas > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Openzaurus-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openzaurus-devel > |
From: Thomas K. <tho...@gm...> - 2007-04-10 18:04:57
|
Hi, I wrote a SPI Driver for Collie. All my SD Cards work on Collie now. Patches can be found at http://www2.informatik.hu-berlin.de/~tkunze/zaurus/patches . The important ones for mmc are: locomo-r0.patch: -fixes GPIO direction setting -implements SPI irq setting locomo_spi-r2.patch -the spi driver mmc_spi-r2.patch -from LKML with very little changes by me The other patches worth noting: collie-kexec.patch - fix kexec for collie collie-r3.patch - refreshed patch from OE - fix boottime serial console output All other patches are refreshed versions of the patches in OE. I would appreciate comments and suggestions. Cheers, Thomas |
From: Henry v. T. <hvo...@sb...> - 2007-04-09 15:52:51
|
Filed as http://bugs.openembedded.org/show_bug.cgi?id=2096 Henry von Tresckow wrote: > Frederico, > I think the problem is actually somewhere in the power management code. > I tried to build my own serial cable yesterday and while diagnosing it, > I discovered that the 3.3V output on Pin 11 of the I/O connector was not > working. I just booted into the maintainance (OK+Cancel) screen, and > the 3.3V works again. The reason for your serial problems is that the > cable has internal components that are powered from this 3.3V output. > |
From: Henry v. T. <hvo...@sb...> - 2007-04-09 14:57:37
|
Frederico, I think the problem is actually somewhere in the power management code. I tried to build my own serial cable yesterday and while diagnosing it, I discovered that the 3.3V output on Pin 11 of the I/O connector was not working. I just booted into the maintainance (OK+Cancel) screen, and the 3.3V works again. The reason for your serial problems is that the cable has internal components that are powered from this 3.3V output. Federico Ruiz wrote: > Hi list! > > I managed to get openzaurus-3.5.5 + kernel 2.6.20 running in my > poodle. Everything I usually use is working (opie+ratoc CFU1.1 usb > host controller + usb devices, and a lot of programs). But there is an > exception: ttyS0 serial console. With kernel 2.4.18 I was using the > serial console plus a particular cable > (http://serialio.com/products/adaptors/ZThinCable.php) to connect the > zaurus to a gps receiver (rs232). gpsd worked fine with that > configuration. Even I was able to use minicom to get some strings out > of the gps. > Now in kernel 2.6.20 (or 2.6.17) I don't get anything from the serial > port. There are no kernel errors or nothing. The problem is that I > don't receive any data from the serial port. > I used minicom to try to comunicate to my gps. I configured all the > serial port settings (hardware and software flow control off, baud > rate, etc) in the right way. > I also play around with stty with no luck. > If I flash back my zaurus to any openzaurus with kernel 2.4 the > communication starts to work again. > I think there is a connection with this problem in here: > http://sourceforge.net/mailarchive/message.php?msg_id=45BCA447.7050502%40alumni.cse.cuhk.edu.hk > but not sure. > Is this a bug of the PXA serial driver in the kernel? (it looks like) > Anybody else with the same problem? > Any ideas what could be wrong? > > PS: I disabled the ttyS0 console connection in the inittab and then > init q to reload the new configuration. > > Regards, > Federico Ruiz. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Openzaurus-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openzaurus-devel > > |
From: Federico R. <mem...@gm...> - 2007-04-09 13:50:15
|
Hi list! I managed to get openzaurus-3.5.5 + kernel 2.6.20 running in my poodle. Everything I usually use is working (opie+ratoc CFU1.1 usb host controller + usb devices, and a lot of programs). But there is an exception: ttyS0 serial console. With kernel 2.4.18 I was using the serial console plus a particular cable (http://serialio.com/products/adaptors/ZThinCable.php) to connect the zaurus to a gps receiver (rs232). gpsd worked fine with that configuration. Even I was able to use minicom to get some strings out of the gps. Now in kernel 2.6.20 (or 2.6.17) I don't get anything from the serial port. There are no kernel errors or nothing. The problem is that I don't receive any data from the serial port. I used minicom to try to comunicate to my gps. I configured all the serial port settings (hardware and software flow control off, baud rate, etc) in the right way. I also play around with stty with no luck. If I flash back my zaurus to any openzaurus with kernel 2.4 the communication starts to work again. I think there is a connection with this problem in here: http://sourceforge.net/mailarchive/message.php?msg_id=45BCA447.7050502%40alumni.cse.cuhk.edu.hk but not sure. Is this a bug of the PXA serial driver in the kernel? (it looks like) Anybody else with the same problem? Any ideas what could be wrong? PS: I disabled the ttyS0 console connection in the inittab and then init q to reload the new configuration. Regards, Federico Ruiz. |
From: Tim C. <ch...@co...> - 2007-04-05 08:19:27
|
On Wednesday 04 April 2007 14:56, Steven Newbury wrote: > You're going to connect a BT radio to the BTUART? I didn't realize > that was exposed through the connector, or are you going to use the > regular UART? Definitely a better solution than using up the CF slot > anyway. The regular one. I actually might not bother now, as I got SCO working over the USB port - I originally thought that the zaurus USB host did not support ISOCHRONUS pipes, but it appears it does, and I had not selected the right options for the hci-usb kernel module. I have used the serial port on the back connector before, when I had a crashing kernel module and needed to get the crash dump out of somewhere. Thanks, Tim |
From: Steven N. <s_j...@ya...> - 2007-04-04 13:56:58
|
--- Tim Chick <ch...@co...> wrote: > On Wednesday 04 April 2007 14:02, Steven Newbury wrote: > > --- Tim Chick <ch...@co...> wrote: > > > The other thing I'm playing with is bluetooth - normal voice (so > > > you can use bluetooth headsets with a voip app HFP/SCO), and stereo > > > audio for watching movies with sound over bluetooth (A2DP). I'll > > > let the list know when I get somewhere with this. > > > > Do you have a bluetooth card that works at a decent speed? I've > > tried a couple and I haven't been able to get above 115200bps even > > though one of them (Billionton) will only interface at 921600!?! I > > have played with the audio interfacing with my phone but I don't own > > a headset to play with. Mostly I just use the bluetooth for NAP/DUN > > and SMS through my phone. > > > Yes, the ambicom bt2000c PCMCIA one connects at 400kbps or so, despite > claiming to connect at 57k. I got it from addonsworld.co.uk. The entry > in the cacko pcmcia database appears to be wrong though - you need to > change it to match the real card identifier string. > > This still isn't enough for A2DP - you need USB or 1Mbps for that. I got > the UART running on the back of the Z, and will be using that with BT > soon. You're going to connect a BT radio to the BTUART? I didn't realize that was exposed through the connector, or are you going to use the regular UART? Definitely a better solution than using up the CF slot anyway. Steve ___________________________________________________________ All New Yahoo! Mail Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html |
From: Tim C. <ch...@co...> - 2007-04-04 13:25:22
|
On Wednesday 04 April 2007 14:02, Steven Newbury wrote: > --- Tim Chick <ch...@co...> wrote: > > The other thing I'm playing with is bluetooth - normal voice (so > > you can use bluetooth headsets with a voip app HFP/SCO), and stereo > > audio for watching movies with sound over bluetooth (A2DP). I'll > > let the list know when I get somewhere with this. > > Do you have a bluetooth card that works at a decent speed? I've > tried a couple and I haven't been able to get above 115200bps even > though one of them (Billionton) will only interface at 921600!?! I > have played with the audio interfacing with my phone but I don't own > a headset to play with. Mostly I just use the bluetooth for NAP/DUN > and SMS through my phone. > Yes, the ambicom bt2000c PCMCIA one connects at 400kbps or so, despite claiming to connect at 57k. I got it from addonsworld.co.uk. The entry in the cacko pcmcia database appears to be wrong though - you need to change it to match the real card identifier string. This still isn't enough for A2DP - you need USB or 1Mbps for that. I got the UART running on the back of the Z, and will be using that with BT soon. Cheers, Tim |
From: Steven N. <s_j...@ya...> - 2007-04-04 13:04:31
|
--- Tim Chick <ch...@co...> wrote: > > The other thing I'm playing with is bluetooth - normal voice (so you can > use bluetooth headsets with a voip app HFP/SCO), and stereo audio for > watching movies with sound over bluetooth (A2DP). I'll let the list > know when I get somewhere with this. Do you have a bluetooth card that works at a decent speed? I've tried a couple and I haven't been able to get above 115200bps even though one of them (Billionton) will only interface at 921600!?! I have played with the audio interfacing with my phone but I don't own a headset to play with. Mostly I just use the bluetooth for NAP/DUN and SMS through my phone. Steve ___________________________________________________________ All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html |
From: Tim C. <ch...@co...> - 2007-04-04 12:45:09
|
On Wednesday 04 April 2007 12:00, Steven Newbury wrote: > Hi Tim, > I'm working on (ARM EABI) Gentoo for Zaurus, have you pushed the pxa > vo driver upstream or is there somewhere I can download it from? For > what it's worth, I'm using gcc-4.2 with arm-iwmmxt-linux-gnueabi and > using -ftree-vectorize for the whole distribution, it's getting > pretty good performance! ;-) > I have got my patch for actually using iwmmxt in mplayer into the upstream ffmpeg/libavcodec project. I have one other very small improvement to libavcodec, which I'm waiting to get submitted. The vo_pxa stuff is in the openembedded monotone repository, as a patch for mplayer, thanks to Graeme. The other thing I'm playing with is bluetooth - normal voice (so you can use bluetooth headsets with a voip app HFP/SCO), and stereo audio for watching movies with sound over bluetooth (A2DP). I'll let the list know when I get somewhere with this. Thanks, Tim |