All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Uli Luckas <u.luckas@road.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Kexec Cmdline Support
Date: Tue, 25 Sep 2007 18:41:45 +0300	[thread overview]
Message-ID: <1577324081.20070925184145@gmail.com> (raw)
In-Reply-To: <200709251620.52994.u.luckas@road.de>

Hello Uli,

Tuesday, September 25, 2007, 5:20:52 PM, you wrote:

> On Monday, 24. September 2007, Hans Henry von Tresckow wrote:
>> (sorry for crossposting this,but I think more of the interested parties
>> read oe-devel then angstrom-devel)
>>
>> A while back, mwester made some patches to add the ability to modify the
>> cmdline when using kexec to load a kernel. I did some testing on poodle and
>> posted the results on the bug tracker
>> (http://bugs.openembedded.org/show_bug.cgi?id=2969)
>> I was wondering what the rest of the developers think of these. 
> Hi Henry,
> A while back I posted a different approach [1] to this mailing list for
> review. To bad, there have not been any comments.

> The differences of my approach in contrast to mwester's approach have been
> discussed on the arm kernel mailing list. If there is any interest in this
> (userspace) approach at all, I will improve on the known problems (like hard
> coded ATAG base address).

> I'd really appreciate feedback from the developers.

  Full commandline, etc. support for kexec is much, much needed
feature. Unfortunately, most developers are likely busy with more
mundane stuff and give good review/testing to it. But those who're
interested in this area for sure should apply such patches to the
device kernel they can test, to facilitate wider testing, and the
authors of the patches for sure should post the for review to general
Linux list, and hopefully communicate to find the best solution.

> Best regerds
> Uli

> 1) 
> http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-August/002840.html



-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  reply	other threads:[~2007-09-25 15:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a7f8874a0709212103h126eeea7y751fa5fd4256fb20@mail.gmail.com>
2007-09-24 19:17 ` RFC: Kexec Cmdline Support Hans Henry von Tresckow
2007-09-25 14:20   ` Uli Luckas
2007-09-25 15:41     ` Paul Sokolovsky [this message]
2007-09-25 16:14     ` Hans Henry von Tresckow
2007-09-26  7:21       ` Uli Luckas
2007-09-26 14:29         ` Hans Henry von Tresckow
2007-09-26 16:01           ` Uli Luckas
2007-10-09 21:02             ` Hans Henry von Tresckow
     [not found]               ` <200710192235.46408.luckas@musoft.de>
2007-10-19 20:46                 ` Hans Henry von Tresckow
2007-10-20  7:46                   ` Koen Kooi
2007-11-02 14:48                 ` Hans Henry von Tresckow
2007-11-06  9:48                   ` Uli Luckas
2007-11-06 17:41                     ` Hans Henry von Tresckow

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=1577324081.20070925184145@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=u.luckas@road.de \
    /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.