All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael <trimarchi@gandalf.sssup.it>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ramdisk problem (once again?)
Date: Wed, 13 Feb 2008 12:07:50 +0100	[thread overview]
Message-ID: <47B2CF86.2080501@gandalf.sssup.it> (raw)
In-Reply-To: <20080212230705.EC29E24050@gemini.denx.de>

Wolfgang Denk wrote:
> In message <47B2202A.7000807@gandalf.sssup.it> you wrote:
>   
>>> The kernel.org tree does not recognize  a  ramdisk  image  in  flash.
>>> Patches  have  been posted here since 2.4.17 times, but never made it
>>> upstream. See the archives ...
>>>   
>>>       
>> If you want to use it, put in ram before... Regards Michael
>>     
>
> yesm that's the status quo - but it's plain stupid. Why  add  another
>   
I just answer to the question.
> memory  copy of megabytes of data, when the kernel will just read the
> data, uncompres it and write it to some  (other)  RAM  location?  The
> flash  is mapped anyway (normally), so it just has to check if it's a
> RAM or flash address to decide if it should free that  area  or  not.
> That's a tiny patch, actually.
>   
Regards Michael

  reply	other threads:[~2008-02-13 11:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12  8:30 [U-Boot-Users] ramdisk problem (once again?) Miguel Angel Alvarez
2008-02-12 22:36 ` Wolfgang Denk
2008-02-12 22:39   ` michael
2008-02-12 23:07     ` Wolfgang Denk
2008-02-13 11:07       ` michael [this message]
2008-02-14 14:10   ` Miguel Angel Alvarez
2008-02-20  6:37 ` Nethra
2008-02-21 19:04   ` [U-Boot-Users] ramdisk problem (once again?) - Solved Miguel Angel Alvarez
2008-02-21 19:45     ` [U-Boot-Users] Taishan linker problem k b
2008-02-21 20:43       ` Wolfgang Denk

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=47B2CF86.2080501@gandalf.sssup.it \
    --to=trimarchi@gandalf.sssup.it \
    --cc=u-boot@lists.denx.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.