mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Xu Yang" <risingsunxy@googlemail.com>
To: "Uli Luckas" <u.luckas@road.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: parse_tag_ramdisk
Date: Fri, 31 Aug 2007 18:08:04 +0200	[thread overview]
Message-ID: <ab40e9c0708310908o38633ecpdbcae78aca15946f@mail.gmail.com> (raw)
In-Reply-To: <200708301846.09669.u.luckas@road.de>

Hi Uli,

thanks ,

I just found in the bootloader I used "go" to access the kernel, maybe
the problem is caused by this, I will check it further.
by the way, do you know how to setup the address of the ramdisk in the
bootloader? I used bootm kernel_address ramdisk_address.

is this enough?

regards,

Yang


2007/8/30, Uli Luckas <u.luckas@road.de>:
> On Thursday, 30. August 2007, Xu Yang wrote:
> > Hi Uli,
> >
> >
> > thanks for your reply.
> >
> > just have a question, where is the tag list, how can i modify this?
> >
> If you don't know where the list is created, how do you now that it contains a
> ramdisk tag? There is a chance, that the kernel does not even get a ram disk
> tag at all. This would also explain, why it is not parsed ;-)
>
> The tag list is supplied by your bootloader. How the bootloader creates the
> list and how to change the order depends on your bootloader. You probably
> have to read (and patch) it's source code.
>
> 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
>

      reply	other threads:[~2007-08-31 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 14:07 parse_tag_ramdisk Xu Yang
2007-08-30 16:06 ` parse_tag_ramdisk Uli Luckas
2007-08-30 16:10   ` parse_tag_ramdisk Xu Yang
2007-08-30 16:46     ` parse_tag_ramdisk Uli Luckas
2007-08-31 16:08       ` Xu Yang [this message]

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=ab40e9c0708310908o38633ecpdbcae78aca15946f@mail.gmail.com \
    --to=risingsunxy@googlemail.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome