From: Uli Luckas <u.luckas@road.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATHC] ATAG export for the linux kernel
Date: Mon, 10 Dec 2007 09:56:22 +0000 [thread overview]
Message-ID: <475D0D46.2030303@road.de> (raw)
In-Reply-To: <1197275254.4804.8.camel@localhost.localdomain>
On Friday, 7. December 2007, Hans Henry von Tresckow wrote:
> On Dec 7, 2007 3:38 AM, Richard Purdie <rpurdie@rpsys.net> wrote:
> > On Fri, 2007-12-07 at 11:06 +0000, Uli Luckas wrote:
> > > Hans Henry, thanks for testing. Good to know it worked for you. Let's
> > > see how we can get this thing pushed upstream.
> > >
> > > 1) I put this on the OE list as the original code is maintained
in OE.
> >
> > And
> >
> > > that's why I'd like the code to be pushed to the OE repository first.
> > > I am not really an OE developer though. Is someone willing to do
the OE
> > > integration to give my patch a home?
> >
> > I'm happy for the userspace side of things to be added in OE. I have
> > some reservations about the way the kernel patch is added to the zaurus
> > code, particularly about the way the kernel commandline is handled
from
> > the broken bootloader and I need to find some time to look at that. I'm
> > fine with the patch in principle though, I just want it right when its
> > added (and preferably upstream too, the existing zaurus changes
will not
> > be accepted upstream).
> >
> > > 2) I need to push the kernel patch via Russell. Mike, I have not
heard
> > your opinion. Will you support this patch?
> > >
> > > 3) I need to push my userspace work. My work is based on code by
> > > Richard though. Richard, please jump in and let us know how you'd
like
> > > to
> >
> > proceede?
> >
> > I did try and find the kexec-tools maintainer but got distracted and
> > never got back to it. Does anyone know who we need to send this to? I
> > will try and get that done this weekend...
> >
> > > I'd really like to see kexec working on arm without any patches soon.
> >
> > Agreed. I'm sorry I haven't found time to look at this yet, I will try
> > hard to do so this weekend.
> >
> > Regards,
> >
> > Richard
> >
> >
> >
> > Richard,
>
> I updated http://bugs.openembedded.org/show_bug.cgi?id=3397 with a new
> patch to filter out the Sharp command line (for poodle at least). Let me
> know if that approach makes more sense.
>
I think I am missing something here. Didn't you (Hans Henry) report my
kernel
patch to work on poodle?
As I don't have a Sharp, could someone clue me in what problem you guys are
trying to sove here?
> http://bugs.openembedded.org/show_bug.cgi?id=3430 has the userspace kexec
> patch.
>
Thanks for forwarding the patch to the right channel.
Regards,
Uli
--
------- ROAD ...the handyPC Company - - - ) ) )
Uli Luckas
Software Development
ROAD GmbH
Bennigsenstr. 14 | 12159 Berlin | Germany
fon: +49 (30) 230069 - 64 | fax: +49 (30) 230069 - 69
url: www.road.de
Amtsgericht Charlottenburg: HRB 96688 B
Managing directors: Hans-Peter Constien, Hubertus von Streit
next prev parent reply other threads:[~2007-12-10 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 9:44 [PATHC] ATAG export for the linux kernel Uli Luckas
2007-11-12 10:02 ` Uli Luckas
2007-12-05 21:06 ` Hans Henry von Tresckow
2007-12-07 11:06 ` Uli Luckas
2007-12-07 11:38 ` Richard Purdie
2007-12-07 16:18 ` Hans Henry von Tresckow
2007-12-10 8:27 ` Richard Purdie
2007-12-10 9:56 ` Uli Luckas [this message]
2007-12-10 13:43 ` Richard Purdie
2007-12-10 15:36 ` Hans Henry von Tresckow
2007-12-10 10:26 ` Uli Luckas
2007-12-10 13:35 ` Richard Purdie
2007-12-11 1:20 ` Uli Luckas
2007-12-10 14:13 ` Mike (mwester)
2007-12-10 10:21 ` Uli Luckas
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=475D0D46.2030303@road.de \
--to=u.luckas@road.de \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.