From: "Mike Frysinger" <vapier.adi@gmail.com>
To: Glenn Henshaw <thraxisp@logicaloutcome.ca>
Cc: linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: Kernel boot problem on IXP422 Rev. A
Date: Thu, 12 Jun 2008 17:35:14 -0400 [thread overview]
Message-ID: <8bd0f97a0806121435r2ace2c5br692cab8426966ee6@mail.gmail.com> (raw)
In-Reply-To: <17882748-2E1B-4DB4-82FD-C5D5C4E62CC8@logicaloutcome.ca>
On Thu, Jun 12, 2008 at 5:28 PM, Glenn Henshaw wrote:
> On 12-Jun-08, at 4:04 PM, Mike Frysinger wrote:
>> On Thu, Jun 12, 2008 at 3:35 PM, Marcus Tangermann wrote:
>>> we currently try to boot a 2.6.21 kernel
>>
>> time to upgrade
>
> Wrong answer!!!
not really
> Many embedded devices can't upgrade kernels easily because of customer
> <snip>
and there are plenty of *wrong* reasons that people are using old kernels.
> Often developers not working in the embedded space don't understand this
> reality.
if i'm not classified as an embedded developer, then i dont know what one is :P
> Helpful responses on what does/does not work would be more appreciated.
i gave a realistic one and i sent him to the right place -- the arm
kernel mailing lists
-mike
next prev parent reply other threads:[~2008-06-12 21:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 19:35 Kernel boot problem on IXP422 Rev. A Marcus Tangermann
2008-06-12 20:04 ` Mike Frysinger
2008-06-12 21:28 ` Glenn Henshaw
2008-06-12 21:35 ` Mike Frysinger [this message]
2008-06-12 21:43 ` Craig Hollabaugh
2008-06-12 21:43 ` Alexey Zaytsev
2008-06-12 22:15 ` David Woodhouse
2008-06-13 17:33 ` Rob Landley
2008-06-13 20:05 ` Tim Bird
2008-06-15 19:17 ` Rob Landley
2008-06-13 0:13 ` Glenn Henshaw
2008-06-13 0:16 ` Greg Ungerer
2008-06-13 19:07 ` Marcus Tangermann
2008-06-14 7:17 ` Greg Ungerer
2008-06-19 17:59 ` Marcus Tangermann
2008-06-20 0:08 ` Greg Ungerer
2008-06-13 2:10 ` George G. Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8bd0f97a0806121435r2ace2c5br692cab8426966ee6@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=thraxisp@logicaloutcome.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).