![]() |
![]() |
![]()
Post
#1
|
|
![]() Group: Members Posts: 497 Joined: 17-January 04 From: St. Louis, USA Member No.: 1,478 ![]() |
Get it here: Get Angstrom Unstable Release for tosa The latest tested release is r8 (kernel 2.6.23).
Working out-of-box altboot with loopback image or direct fs Kernel 2.6.23 (testing 2.6.24 for >= r9) Tosa kernel status from Dmitry Images: Opie 1.2.3 (core opie application feed, other opie or qt applications not in the feed yet) and GPE 2.8 (x11-image) with match-box as default WM Keyboard (keymap changed in 2.6.24) Internal Wifi (wlan-ng-modules-usb 2.8) 802.11b WEP only, no WPA SD: non-sdhc or sdhc (tested with 4GB card of both) CF and 2nd CF on sled OE Tosa Meta-Bug Outstanding critical bugs: 1. suspend/resume OE bug 2134 [Closed] 2. sound system OE bug 3518 Speaker/Headphone tested working. Mic/phone untested Major bugs: [Hacked kdrive in x11-image to overcome the problem, still an issue in opie-image] 1. frame buffer (a.k.a, screen corruption or the famous yellow vertical lines) : occurs "occasionally" with 2.6.23 kernel, much better than "often" with 2.6.17 kernel OE bug 490 Opie bugs: file Opie bug tracker GPE bugs: file GPE bug tracker Kernel, roofs or packaging bugs: file OE bug tracker Not tested yet: ?USB host ?Speaker/Headphone/Headset/Mic (need to fix the alsa state in r9) USB client USB network Mic (the one on the back of the device) / PhoneMic (2.5mm jack used with a headset) etc. This post has been edited by xjqian: Jun 19 2008, 12:17 AM |
|
|
![]() |
![]()
Post
#2
|
|
![]() Group: Members Posts: 232 Joined: 26-September 03 Member No.: 500 ![]() |
I asked on the mailing list, but didn't get a reply so I thought I'd ask here.
All of the 2008.x images in the autobuild dir are gone, and only kexec images are there. I have used the narcissus images in the past successfully to boot Angstrom with either Opie or x11 for Tosa (via SD w/ kexec kernel). Lately the images have not been completing the configuration of kernel modules. In particular, kernel-module-zlib-inflate gets stuck (can't get past it - Tosa requires a reset). I'm curious if anyone is still doing kernel dev for the tosa (it was lumaq {letic?}). Is there any way to follow development if it is still going on? I love the device, and I'd love to continue using it if I can. Thanks, Russell Dwiggins |
|
|
![]() ![]() |
![]() |
Lo-Fi Version | Time is now: 22nd April 2018 - 04:30 AM |