Re: [QtExtended] latest andy-tracking kernel
So, it's ok with fso image from 02-29-09. i will tell you for tracking bugs 2009/4/15 Sound Freedom > I tested fso-image from 04/04/09 & kernel from your site (links on the > comment of your script) then I couldn't get usb network. > My computer*S* tell me that ther is no usb such device. > > I'm trying a new install with second links of your comment (with fso-image > from 29-02-09) & tell you if it'll be ok > > 2009/4/14 Franky Van Liedekerke > > On Tue, 14 Apr 2009 22:30:28 +0200 >> Sander van Grieken wrote: >> >> > On Tuesday 14 April 2009 21:54:53 Franky Van Liedekerke wrote: >> > > Maybe the latest version is ok again, but it is IMPOSSIBLE TO TEST >> > > since ssh no longer works. Surely somebody must notice this, or is >> > > nobody even using these images? >> > >> > Yeah I noticed too, but I assumed I b0rked my build system, since I >> > tried to use the SHR overlay manually.. also, X didn't start anymore, >> > that's when I noticed SSH didn't work. >> > >> > but, while waiting for the entire rebuild to finish, I'm taking a >> > look at the commits since April 4 :) >> >> well, I don't know, but reverting to that kernel+rootf fixed the >> incoming SMS when suspended thing. >> But now the whole missed-call comes flying back to me: whenever I >> answer a call, the second after I pressed "answer", a new call >> notification pops up saying I have the same incoming call. >> Seems like a timing issue to me ... propably something in >> qmodemcallprovider.cpp that should be redefined in vendor_neo.cpp >> >> Franky >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community >> > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtExtended] latest andy-tracking kernel
I tested fso-image from 04/04/09 & kernel from your site (links on the comment of your script) then I couldn't get usb network. My computer*S* tell me that ther is no usb such device. I'm trying a new install with second links of your comment (with fso-image from 29-02-09) & tell you if it'll be ok 2009/4/14 Franky Van Liedekerke > On Tue, 14 Apr 2009 22:30:28 +0200 > Sander van Grieken wrote: > > > On Tuesday 14 April 2009 21:54:53 Franky Van Liedekerke wrote: > > > Maybe the latest version is ok again, but it is IMPOSSIBLE TO TEST > > > since ssh no longer works. Surely somebody must notice this, or is > > > nobody even using these images? > > > > Yeah I noticed too, but I assumed I b0rked my build system, since I > > tried to use the SHR overlay manually.. also, X didn't start anymore, > > that's when I noticed SSH didn't work. > > > > but, while waiting for the entire rebuild to finish, I'm taking a > > look at the commits since April 4 :) > > well, I don't know, but reverting to that kernel+rootf fixed the > incoming SMS when suspended thing. > But now the whole missed-call comes flying back to me: whenever I > answer a call, the second after I pressed "answer", a new call > notification pops up saying I have the same incoming call. > Seems like a timing issue to me ... propably something in > qmodemcallprovider.cpp that should be redefined in vendor_neo.cpp > > Franky > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtExtended] missed call trace (was: latest andy-tracking kernel)
On Tue, 14 Apr 2009 23:25:56 +0200
Franky Van Liedekerke wrote:
> On Tue, 14 Apr 2009 22:30:28 +0200
> Sander van Grieken wrote:
>
> > On Tuesday 14 April 2009 21:54:53 Franky Van Liedekerke wrote:
> > > Maybe the latest version is ok again, but it is IMPOSSIBLE TO TEST
> > > since ssh no longer works. Surely somebody must notice this, or is
> > > nobody even using these images?
> >
> > Yeah I noticed too, but I assumed I b0rked my build system, since I
> > tried to use the SHR overlay manually.. also, X didn't start
> > anymore, that's when I noticed SSH didn't work.
> >
> > but, while waiting for the entire rebuild to finish, I'm taking a
> > look at the commits since April 4 :)
>
> well, I don't know, but reverting to that kernel+rootf fixed the
> incoming SMS when suspended thing.
> But now the whole missed-call comes flying back to me: whenever I
> answer a call, the second after I pressed "answer", a new call
> notification pops up saying I have the same incoming call.
> Seems like a timing issue to me ... propably something in
> qmodemcallprovider.cpp that should be redefined in vendor_neo.cpp
>
> Franky
>
ok, for those curious: I've put online a AT-listing of a missed call:
http://users.telenet.be/liedekef/missedcall.txt
The scenario is this: call the device from another line, answer the
call and watch a notification for a second call arrive (sometimes).
The AT commands in the text file are of course the results of both
calls, so it can be a bit confusing. Although the AT-call "ATA" should
give you a hint that the device in the end thinks there is only one
active call (otherwise it would be AT+CHLD=2).
I think the cause of the problems lies in the function
void QModemCallProvider::clccIncoming()
in the file src/libraries/qtopiaphonemodem/qmodemcallprovider.cpp
Specifically this part seems to be the culprit:
if ( callType.isEmpty() ) {
// We could not determine the call type, so the incoming call
// has probably disappeared. Flag it as a missed voice call.
d->incomingCallType = "Voice"; // No tr
announceCall();
d->missedTimer->stop();
missedTimeout();
} else {
This part makes sure that for a call that can't be identified, the call
gets announced and then flagged as being missed, exactly what I see in
the logfile.
Now I don't get this: why flag an dissapeared call of unknown type as
voice and missed call?
>From what I can see, this code should be:
if ( callType.isEmpty() ) {
// We could not determine the call type, so the incoming call
// has probably disappeared. Ignore it.
stopRingTimers();
} else {
Any comments on this?
Ok, the fact that the modem sends an extra RING after the call is
accepted is probably because it's a bit slow sometimes (or the RING
arrives a bit too slow).
Franky
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [QtExtended] latest andy-tracking kernel
On Tue, 14 Apr 2009 22:30:28 +0200 Sander van Grieken wrote: > On Tuesday 14 April 2009 21:54:53 Franky Van Liedekerke wrote: > > Maybe the latest version is ok again, but it is IMPOSSIBLE TO TEST > > since ssh no longer works. Surely somebody must notice this, or is > > nobody even using these images? > > Yeah I noticed too, but I assumed I b0rked my build system, since I > tried to use the SHR overlay manually.. also, X didn't start anymore, > that's when I noticed SSH didn't work. > > but, while waiting for the entire rebuild to finish, I'm taking a > look at the commits since April 4 :) well, I don't know, but reverting to that kernel+rootf fixed the incoming SMS when suspended thing. But now the whole missed-call comes flying back to me: whenever I answer a call, the second after I pressed "answer", a new call notification pops up saying I have the same incoming call. Seems like a timing issue to me ... propably something in qmodemcallprovider.cpp that should be redefined in vendor_neo.cpp Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtExtended] latest andy-tracking kernel
On Tuesday 14 April 2009 21:54:53 Franky Van Liedekerke wrote: > Maybe the latest version is ok again, but it is IMPOSSIBLE TO TEST > since ssh no longer works. Surely somebody must notice this, or is > nobody even using these images? Yeah I noticed too, but I assumed I b0rked my build system, since I tried to use the SHR overlay manually.. also, X didn't start anymore, that's when I noticed SSH didn't work. but, while waiting for the entire rebuild to finish, I'm taking a look at the commits since April 4 :) grtz, Sander ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtExtended] latest andy-tracking kernel
Hi all, just to let you know: I tried the latest andy-tracking kernel (gitr10 and gitr11 even) together with an older fso-nox image (from April 4, because newer fso images don't give me ssh access anymore). This combo proves to be troublesome: no wake-up on sms receiving, missed-calls for every incoming call, etc ... not good. In the end, I couldn't even place a call anymore ... So: don't use this combo. I recommend the stable 2.6.28 kernel with accompanying rootfs or uImage-2.6.28-andy-tracking+gitr6+9c4451ff31b937a478f3d3eabef30b71cbe12b12-r3-om-gta02.bin with fso-nox image from April 4. It seems the best to take the jffs and the kernel from the same build. Then run my install script on it. Maybe the latest version is ok again, but it is IMPOSSIBLE TO TEST since ssh no longer works. Surely somebody must notice this, or is nobody even using these images? Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unstable andy-tracking kernel
You don't have to install whole image, you can install only kernel and modules on your existing rootfs. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unstable andy-tracking kernel
On Fri, 10 Apr 2009 16:07:53 +0200 Johny Tenfinger wrote: > shr-unstable is using andy-tracking with AUTOREV, so you can download > it from http://build.shr-project.org/ I see, I thought that 2.6.28-oe1-* was based on the stable one ... Now just a shr rootfs that's a bit more lightweight :-) Something the fso-nox images would be very nice, now I need to flash 48M and then ditch most of it. Or maybe I should just start building the latest andy-tracking myself, but I'm pretty sure that SHR can come up with a more "basic" image, no? Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unstable andy-tracking kernel
shr-unstable is using andy-tracking with AUTOREV, so you can download it from http://build.shr-project.org/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
unstable andy-tracking kernel
Hi all, untill a couple of days ago, I was able to download the latest andy-tracking kernel from http://downloads.openmoko.org/distro/unstable/daily/ but for some reason (maybe because a build fails, but not according to tinderbox (http://tinderbox.openembedded.net/packages/469221/), these kernel images aren't there anymore. And in all older directories, the andy-tracking was removed on a daily basis as well (was like this always I think). Is there another place for me to download the latest andy-tracking bin file? Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
After installing all possible kerners, bootloaders and kernels to get rid of the WSOD (not after susped, just at any possible moment, when i'm not touching the device) I installed QI and the andy-tracking kernel. But my power down button does not work any more, usb as well( also not after some reboots), The problem is that I can't really reboot any more, only removing the battery. The button does work to get the neo back out of suspend. Anyone had this problem as well? My device is Neo Freerunner QI: qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu kernel: uImage-moredrivers-GTA02_andy-tracking-d1a9cf85c8608601.bin and uImage-moredrivers-GTA02_andy-tracking-15ca3dafb2662db4.bin thx in advance Maarten -- View this message in context: http://n2.nabble.com/andy-tracking-kernel--tp1609293p2455929.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Thu, 2008-12-04 at 13:54 +0100, arne anka wrote: |>> improved in andy-tracking. If it's due to firmware trouble, probably |>> this will never be fixed due to Atheros closed firmware policies. |> wasn't there recently a release of an completely open atheros driver? |>> http://www.heise-online.co.uk/news/MadWifi-HAL-now-open-source--/112113 |> or did that not apply to the chip used in the fr? | | There are working drivers for ath5k and ath9k, but the Neo has an | ath6k ... Yes the main difference is that the AR6001 in GTA02 is what's called a "fullmac" device, it means that it has an 80211 stack in the firmware of the device that can run autonomously. That's in contrast to the other devices which use a "softmac" 80211 stack in Linux. The advantage is that it can run autonomously somewhat even with Linux down, the disadvantage is we are entirely at the mercy of the not-really-updateable closed firmware for a very wide range of operations. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3164ACgkQOjLpvpq7dMpeMQCaAqluqq4S+c4xiveBgVVMTfvt 5AUAn2cBOrC3CGtoxYsEFU9kPZsJpUPK =VO5V -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
On Thu, 2008-12-04 at 13:54 +0100, arne anka wrote: > > improved in andy-tracking. If it's due to firmware trouble, probably > > this will never be fixed due to Atheros closed firmware policies. > > wasn't there recently a release of an completely open atheros driver? > > http://www.heise-online.co.uk/news/MadWifi-HAL-now-open-source--/112113 > or did that not apply to the chip used in the fr? There are working drivers for ath5k and ath9k, but the Neo has an ath6k ... Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
> improved in andy-tracking. If it's due to firmware trouble, probably > this will never be fixed due to Atheros closed firmware policies. wasn't there recently a release of an completely open atheros driver? > http://www.heise-online.co.uk/news/MadWifi-HAL-now-open-source--/112113 or did that not apply to the chip used in the fr? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
On Thu, 2008-12-04 at 11:38 +, Andy Green wrote: > I must confess that, as I wanted to use my Neo as a sort of > | internet tablet, it now just gathers dust somewhere, waiting for a WiFi > | fix. > > Changing the SDIO stack is enough of a jolt it's probably worth blowing > the dust off and having another go according to your optimism / schedule > :-) At any rate if you do this please post on kernel list about your > experiences. Right, I'll try in my copious spare time. Would it be possible for you to put a small README in your directory, to explain how to use these files ? Even if it's just a pointer to somewhere on the wiki, it'd be great. Thanks, Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> Wifi has been working (for some values of working) for a long while... |> what bad behaviour does "not working" look like for you? | | Well, if you ask for it: | - can only connect through command-line (not that important) Sean McNeil is targeting getting the Android UI for that working at any rate. | - weak signal Weak transmission or RX or both? | - connexion lasts only for a few minutes Hum. | - after connexion is lost, reconnecting nearly always involves rebooting Well, if this is due to SDIO side errors, this situation can have been improved in andy-tracking. If it's due to firmware trouble, probably this will never be fixed due to Atheros closed firmware policies. | I think I already sent the kernel messages that appear in that case | somewhere. I must confess that, as I wanted to use my Neo as a sort of | internet tablet, it now just gathers dust somewhere, waiting for a WiFi | fix. Changing the SDIO stack is enough of a jolt it's probably worth blowing the dust off and having another go according to your optimism / schedule :-) At any rate if you do this please post on kernel list about your experiences. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3wUQACgkQOjLpvpq7dMq3vACfe0uMjBCMueWANbTmtOuPTpvR VPcAn10hXLCc0XNUhX7wF5FacR4OPNRW =V0aw -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
On Thu, 2008-12-04 at 09:55 +, Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | Hi Andy, > | > | On Wed, 2008-12-03 at 16:36 +, Andy Green wrote: > |> ~ - WLAN driver now uses mainline SDIO stack (should fix some probs) > | > | Does that mean WiFi is working now ? > > Wifi has been working (for some values of working) for a long while... > what bad behaviour does "not working" look like for you? Well, if you ask for it: - can only connect through command-line (not that important) - weak signal - connexion lasts only for a few minutes - after connexion is lost, reconnecting nearly always involves rebooting I think I already sent the kernel messages that appear in that case somewhere. I must confess that, as I wanted to use my Neo as a sort of internet tablet, it now just gathers dust somewhere, waiting for a WiFi fix. HTH, Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi Andy, | | On Wed, 2008-12-03 at 16:36 +, Andy Green wrote: |> ~ - WLAN driver now uses mainline SDIO stack (should fix some probs) | | Does that mean WiFi is working now ? Wifi has been working (for some values of working) for a long while... what bad behaviour does "not working" look like for you? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk3qRIACgkQOjLpvpq7dMqofwCgiF7V+PzyU8gggDNphszuwUyT 02QAoI7n1sGzzWGrCL8smhyPg9G4KU9A =9gnV -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
Hi Andy, On Wed, 2008-12-03 at 16:36 +, Andy Green wrote: > ~ - WLAN driver now uses mainline SDIO stack (should fix some probs) Does that mean WiFi is working now ? Thanks, Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
Andy Green wrote:
> Somebody in the thread at some point said:
>
> | I've seen a lot of references to the "andy-tracking" kernel. A search
> | of archives yields some info about this with regard to a shift to the
> | 2.6.27 kernel. However, I've not been able to really understand what's
> | in it, or what the current state of the kernel is.
> |
> | Would someone mind elaborating a little on a few points:
> |
> | 1. Is this generally available? If so, where?
>
> http://people.openmoko.org/andy has new binary versions every day or two
> at the moment. These are "moredriver" kernels that have everything
> critical built in the kernel, but there's also a matching module tarball.
>
> If you're using U-Boot to boot it, U-Boot has a 2MByte kernel limit by
> default and you need to meddle it:
>
> setenv bootcmd setenv bootargs \${bootargs_base} \${mtdparts}\; nand
> read.e 0x3200 kernel 0x30\; bootm 0x3200
> saveenv
>
> Qi (the new bootloader replacing U-Boot) doesn't have these problems.
>
> | 2. I'm currently running Debian with the stock kernel that gets put in
> | place by the install.sh script. Can I use this kernel with Debian?
> | There are caveats on the Debian pages about using other kernel, so has
> | anyone used this with Debian successfully?
>
> Dunno what the caveats involve, I used Debian in runlevel 3 anyway with
> random kernels.
>
> | 3. What do I get with it? What is at risk?
> |
> | Thanks... I apologize if this info is out there somewhere, but I have
> | spent a significant amount of time digging through past threads, and I'm
> | just not getting a complete picture.
>
> You can try it out on an SD Card for very low risk.
>
> The main features are
>
> ~ - Suspend / Resume changes (should be way more stable)
> ~ - pcf50633 driver rewrite (fixes some troubles)
> ~ - WLAN driver now uses mainline SDIO stack (should fix some probs)
> ~ - Android-ready
> ~ - Kernel features and fixes between 2.6.24 and 2.6.28
>
> There will be some breakage of features for a while since there are many
> changes to /sys paths used by various things, but the rootfs people
> should catch up soon.
Yesterday i tried to boot debian from sd-card with andy-tracking kernel
version 2d1d9ec0e2d009d0 and it didn't work very well.
First problem was that it seems to lack support for vfat partitions. I
use a 64MB swapfile which is on a vfat partition used by fstab while
booting. But at the point when activating the swap file it hangs and get
a timeout after 120sec and than do nothing.
After i removed the corresponding fstab line it boots up but the
hal-daemon didn't work anymore with the new kernel. Therefore some
things like the oevents from fso doesn't work anymore. This is maybe
related to the changed sysfs structure.
So at the moment i stay at the 2.6.24 openmoko kernel from the daily
build url as long as the userland tools use the old sysfs values.
Ciao,
Rainer
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I've seen a lot of references to the "andy-tracking" kernel. A search
| of archives yields some info about this with regard to a shift to the
| 2.6.27 kernel. However, I've not been able to really understand what's
| in it, or what the current state of the kernel is.
|
| Would someone mind elaborating a little on a few points:
|
| 1. Is this generally available? If so, where?
http://people.openmoko.org/andy has new binary versions every day or two
at the moment. These are "moredriver" kernels that have everything
critical built in the kernel, but there's also a matching module tarball.
If you're using U-Boot to boot it, U-Boot has a 2MByte kernel limit by
default and you need to meddle it:
setenv bootcmd setenv bootargs \${bootargs_base} \${mtdparts}\; nand
read.e 0x3200 kernel 0x30\; bootm 0x3200
saveenv
Qi (the new bootloader replacing U-Boot) doesn't have these problems.
| 2. I'm currently running Debian with the stock kernel that gets put in
| place by the install.sh script. Can I use this kernel with Debian?
| There are caveats on the Debian pages about using other kernel, so has
| anyone used this with Debian successfully?
Dunno what the caveats involve, I used Debian in runlevel 3 anyway with
random kernels.
| 3. What do I get with it? What is at risk?
|
| Thanks... I apologize if this info is out there somewhere, but I have
| spent a significant amount of time digging through past threads, and I'm
| just not getting a complete picture.
You can try it out on an SD Card for very low risk.
The main features are
~ - Suspend / Resume changes (should be way more stable)
~ - pcf50633 driver rewrite (fixes some troubles)
~ - WLAN driver now uses mainline SDIO stack (should fix some probs)
~ - Android-ready
~ - Kernel features and fixes between 2.6.24 and 2.6.28
There will be some breakage of features for a while since there are many
changes to /sys paths used by various things, but the rootfs people
should catch up soon.
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkk2tW4ACgkQOjLpvpq7dMqgtACcCbAFepKRhdb50dmblBkBe1pS
AkQAn3HzTNMF2cSS9YaeGDHcJnrzC5Co
=cgkB
-END PGP SIGNATURE-
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
On Wed, Dec 3, 2008 at 10:30 AM, Christopher J. White <[EMAIL PROTECTED]> wrote: > I've seen a lot of references to the "andy-tracking" kernel. A search > of archives yields some info about this with regard to a shift to the > 2.6.27 kernel. However, I've not been able to really understand what's > in it, or what the current state of the kernel is. > > Would someone mind elaborating a little on a few points: > > 1. Is this generally available? If so, where? http://people.openmoko.org/andy/ Right now the kernel is bigger than 2MB, and you have to either use Qi as the boot loader (it's still under heavy development now but some people use it) or use U-Boot. For U-boot check: http://lists.openmoko.org/nabble.html#nabble-f528198 I read this kernel will be smaller when it becomes the stable kernel (with a recommended configuration for distributors). You might want to read this email: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006945.html > 2. I'm currently running Debian with the stock kernel that gets put in > place by the install.sh script. Can I use this kernel with Debian? > There are caveats on the Debian pages about using other kernel, so has > anyone used this with Debian successfully? I don't know. Some paths have changed in /sys and some user-space tools will have to change. I don't know how this affects Debian. Check: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006789.html > 3. What do I get with it? What is at risk? I've hear that it has better suspend/resume support. It has some improvements but I don't know about all of them. > Thanks... I apologize if this info is out there somewhere, but I have > spent a significant amount of time digging through past threads, and I'm > just not getting a complete picture. To build from sources you need to: git clone git://git.openmoko.org/git/kernel.git linux-2.6 git-checkout --track -b local-andy-tracking origin/andy-tracking git-pull # it should be up to date cd linux-2.6 cp ./arch/arm/configs/gta02-moredrivers-defconfig .config There's a "build" script that you can run. You need to install a toolchain to build it. For instance, in the build script I use: export CROSS_COMPILE="ccache /usr/local/openmoko/arm/bin/arm-angstrom-linux-gnueabi-" ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking kernel?
You can download it from: http://people.openmoko.org/andy/ It's uImage-moredrivers* As I get it it uses 2.6.28 kernel. The main reason to use it is that a lot of suspend/resume issues have been resolved "out of the box" in this kernel. I tried it and it seems working ok, although I didn't test it much. I also would like to understand what is left to be done in this kernel to get it ready to distribution use. Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
andy-tracking kernel?
I've seen a lot of references to the "andy-tracking" kernel. A search of archives yields some info about this with regard to a shift to the 2.6.27 kernel. However, I've not been able to really understand what's in it, or what the current state of the kernel is. Would someone mind elaborating a little on a few points: 1. Is this generally available? If so, where? 2. I'm currently running Debian with the stock kernel that gets put in place by the install.sh script. Can I use this kernel with Debian? There are caveats on the Debian pages about using other kernel, so has anyone used this with Debian successfully? 3. What do I get with it? What is at risk? Thanks... I apologize if this info is out there somewhere, but I have spent a significant amount of time digging through past threads, and I'm just not getting a complete picture. ...cj ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
