From: Alexey Galakhov <agalakhov@gmail.com>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 4/4] S5PV210 iROM magic boot code
Date: Fri, 04 May 2012 15:47:59 +0600 [thread overview]
Message-ID: <4FA3A5CF.9050503@gmail.com> (raw)
In-Reply-To: <201205031959.57093.jbe@pengutronix.de>
On 03.05.2012 23:59, Juergen Beisert wrote:
> It seems to be a low hanging fruit to use the iROM to access some of the
> peripherals. But there is no way to tell the compiler the calling convention
> to the ROM functions. And the entry points seems guessed only. This results
> into "it works for me with this compiler and these compiler flags and that
> CPU's silicon revision"...
>
> The S3C6410 CPU comes also with such an iROM. But calling it is only useful in
> the first stage loader (and the S3C6410 iROM has a defined jump table to
> call specific functions, there is no need to guess the real entry points).
>
> Writing a Barebox driver for this MMC/SD unit instead should be the correct
> way.
>
> Juergen
Agree.
This function is for 1st stage only. I plan to remove it as soon as MMC
driver will be complete. Right now it is needed, however, to boot 2nd stage.
Right not I have working NAND, DRAM and UART. I plan to get working USB
soon. MMC seems to be (almost) generic SDHCI (very similar to existing
imx driver).
Regards,
Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-05-04 9:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 13:14 [PATCH 0/4] Support Samsung S5PV210 CPU Alexey Galakhov
2012-05-03 13:14 ` [PATCH 1/4] Support most Samsung SoCs in S3C serial driver Alexey Galakhov
2012-05-03 13:14 ` [PATCH 2/4] Fine split S3C arch dependencies from generic code Alexey Galakhov
2012-05-03 17:41 ` Juergen Beisert
2012-05-04 9:39 ` Alexey Galakhov
2012-05-04 9:58 ` Juergen Beisert
2012-05-04 10:50 ` Alexey Galakhov
2012-05-04 11:13 ` Juergen Beisert
2012-05-04 11:26 ` missing sscanf christian.buettner
2012-05-04 11:40 ` [PATCH 2/4] Fine split S3C arch dependencies from generic code Alexey Galakhov
2012-05-04 12:00 ` Juergen Beisert
2012-05-04 12:34 ` Alexey Galakhov
2012-05-04 10:52 ` Alexey Galakhov
2012-05-03 13:14 ` [PATCH 3/4] Minimal S5PV210 + Tiny210 support (2nd stage only) Alexey Galakhov
2012-05-03 17:49 ` Juergen Beisert
2012-05-04 9:41 ` Alexey Galakhov
2012-05-03 13:14 ` [PATCH 4/4] S5PV210 iROM magic boot code Alexey Galakhov
2012-05-03 17:59 ` Juergen Beisert
2012-05-04 9:47 ` Alexey Galakhov [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=4FA3A5CF.9050503@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