public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] OneNAND: Move largepage_memorybased
Date: Tue, 5 Oct 2010 04:36:09 +0200	[thread overview]
Message-ID: <201010050436.09862.marek.vasut@gmail.com> (raw)
In-Reply-To: <AANLkTimEAtdbQNs4P+sAkZVq97UpaY5esD=eihJEC5Wu@mail.gmail.com>

Dne ?t 5. ??jna 2010 04:05:57 Kyungmin Park napsal(a):
> Hi,
> 
> I tested it with the latest u-boot codes. and without OneNAND patch,
> it's boot and working well.
> 
> Of course I used the relocation method at u-boot.

Well is it necessary to expose this stuff so much anyway ? Why can't it be in 
that function?

Besides, in my case, the .data doesn't exist at the place where it was before 
relocation after the relocation is done. With this patch though, I have no 
problems even in that case.

Cheers
> 
> Thank you,
> Kyungmin Park
> 
> On Tue, Oct 5, 2010 at 7:31 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
> > Dne Po 4. ??jna 2010 23:18:51 Scott Wood napsal(a):
> >> On Mon, 4 Oct 2010 23:15:11 +0200
> >> 
> >> Marek Vasut <marek.vasut@gmail.com> wrote:
> >> > Dne Po 4. ??jna 2010 19:59:14 Scott Wood napsal(a):
> >> > > NACK, you're taking the address of stack data and using it after the
> >> > > stack frame goes away.
> >> > 
> >> > The .data section doesn't exist at 0x0 (where the stuff is linked)
> >> > when this code is executed in my case.
> >> 
> >> So fix the linking. :-)
> > 
> > I'd gladly accept any suggestion or if you could point me in a correct
> > direction.
> > 
> >> -Scott
> > 
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot

      reply	other threads:[~2010-10-05  2:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-02 17:33 [U-Boot] [PATCH 1/4] OneNAND: Move largepage_memorybased Marek Vasut
2010-10-02 17:33 ` [U-Boot] [PATCH 2/4] OneNAND: Fixup command table on reloc Marek Vasut
2010-10-02 18:28   ` Minkyu Kang
2010-10-02 18:59     ` Marek Vasut
2010-10-02 19:31       ` Minkyu Kang
2010-10-03 18:21       ` Wolfgang Denk
2010-10-03 19:24         ` Marek Vasut
2010-10-03 21:16           ` Wolfgang Denk
2010-10-03 11:19   ` Sergei Shtylyov
2010-10-03 14:25     ` Marek Vasut
2010-10-03 18:39       ` Wolfgang Denk
2010-10-02 17:33 ` [U-Boot] [PATCH 3/4] OneNAND: Introduce CONFIG_SYS_IPL_LOAD_ADDR Marek Vasut
2010-10-03  6:40   ` Kyungmin Park
2010-10-03 14:25     ` Marek Vasut
2010-10-02 17:33 ` [U-Boot] [PATCH 4/4] OneNAND: Use generic_onenand_read_page in IPL Marek Vasut
2010-10-03  6:40   ` Kyungmin Park
2010-10-03 14:27     ` Marek Vasut
2010-10-03 23:33       ` Marek Vasut
2010-10-03 23:45         ` Kyungmin Park
2010-10-04  0:24           ` Marek Vasut
2010-10-04  6:05             ` Wolfgang Denk
2010-10-14 21:15           ` Marek Vasut
2010-10-04 18:09   ` Scott Wood
2010-10-04  0:23 ` [U-Boot] [PATCH 1/4] OneNAND: Move largepage_memorybased Marek Vasut
2010-10-04 17:59 ` Scott Wood
2010-10-04 21:15   ` Marek Vasut
2010-10-04 21:18     ` Scott Wood
2010-10-04 22:31       ` Marek Vasut
2010-10-05  2:05         ` Kyungmin Park
2010-10-05  2:36           ` Marek Vasut [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=201010050436.09862.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox