mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexey Galakhov <agalakhov@gmail.com>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: [PATCH 3/9] Minimal S5PV210 + Tiny210 support (2nd stage only)
Date: Mon, 14 May 2012 17:07:03 +0600	[thread overview]
Message-ID: <4FB0E757.5050508@gmail.com> (raw)
In-Reply-To: <201205141157.29518.jbe@pengutronix.de>

Hi,

On 14.05.2012 15:57, Juergen Beisert wrote:
> Hi Alexey,
> 
> please keep the mailing list at least on CC.

Oops. Sorry. Wrong button :)

>> Using iROM to boot is generally a bad idea, but there's no alternative
>> right now.
> 
> For you there might be no alternative right now. But for Barebox its all right 
> if only a basic support for this new CPU is available.

Even if it's not bootable?

Ok, there's better plan. Instead of adding iROM in a separate file, I'll
just call its magic address in board's lowlevel init. So this will be
for tiny210 only.

> Skip the iROM entirely in your patch series if you want to remove it later on. 
> What sense would it make to include it and then remove it again?

It depends on what one means "remove again". This may happen after a
year or so. While I think I can implement NAND quite fast, I'm not so
optimistic about MMC.

>> However, there's one bad thing: it's better to add at least one board to
>> Kconfig with the new arch.
> 
> ?

If there are no BOARDINFO and board-y defined, barebox cannot be built.
So one cannot compile barebox with CONFIG_ARCH_something if there are no
boards utilizing it, right? How to test the compilation then? Is it Ok?

Regards,
Alex

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-05-14 11:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12 16:23 [Pull request] Minimal S5PV210 support Alexey Galakhov
2012-05-13  9:09 ` Sascha Hauer
2012-05-13 12:39   ` [PATCH 0/9] " Alexey Galakhov
2012-05-13 12:39     ` [PATCH 1/9] Support most Samsung SoCs in S3C serial driver Alexey Galakhov
2012-05-13 12:39     ` [PATCH 2/9] Fine split S3C arch dependencies from generic code Alexey Galakhov
2012-05-14  8:03       ` Juergen Beisert
2012-05-14  8:54         ` Alexey Galakhov
2012-05-14  8:57           ` Sascha Hauer
2012-05-14  8:59             ` Alexey Galakhov
2012-05-14  9:00           ` Juergen Beisert
2012-05-14  9:30             ` Alexey Galakhov
2012-05-14  8:12       ` Sascha Hauer
2012-05-13 12:40     ` [PATCH 3/9] Minimal S5PV210 + Tiny210 support (2nd stage only) Alexey Galakhov
2012-05-14  8:13       ` Juergen Beisert
2012-05-14  8:57         ` Alexey Galakhov
2012-05-14  9:04           ` Juergen Beisert
     [not found]             ` <4FB0D058.3070206@gmail.com>
2012-05-14  9:57               ` Juergen Beisert
2012-05-14 11:07                 ` Alexey Galakhov [this message]
2012-05-14 13:07                   ` Juergen Beisert
2012-05-14 13:38                     ` Alexey Galakhov
2012-05-13 12:40     ` [PATCH 4/9] S5PV210 iROM magic boot code Alexey Galakhov
2012-05-14  7:51       ` Sascha Hauer
2012-05-14  8:55         ` Alexey Galakhov
2012-05-13 12:40     ` [PATCH 5/9] S5P DRAM support Alexey Galakhov
2012-05-13 12:40     ` [PATCH 6/9] S5P lowlevel clock init Alexey Galakhov
2012-05-13 12:40     ` [PATCH 7/9] Revert "S5PV210 iROM magic boot code" Alexey Galakhov
2012-05-13 12:40     ` [PATCH 8/9] S5P iROM boot support - improved Alexey Galakhov
2012-05-13 12:40     ` [PATCH 9/9] S5P boot header and image generator Alexey Galakhov

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=4FB0E757.5050508@gmail.com \
    --to=agalakhov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=jbe@pengutronix.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