From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 3/8] mips: add base support for atheros ath79 based SOCs
Date: Sat, 26 Dec 2015 18:06:46 +0100 [thread overview]
Message-ID: <201512261806.46935.marex@denx.de> (raw)
In-Reply-To: <567EC7F0.4030909@gmail.com>
On Saturday, December 26, 2015 at 06:01:36 PM, Daniel Schwierzeck wrote:
[...]
> >> This should be C code, pretty please.
> >
> > Must this be change to c code?
> > I think there should be no problem.
>
> this function is only called from init_dram() which already runs in a
> full C environment. The conversion to C should be simple. But I would
> accept the current patch for the initial merge if you do the conversion
> later.
I'm quite opposed to that, we should keep the code out of tree until it's
in sensible state, otherwise it'd only set a bad example. Especially if the
conversion is easy and it has full C env, we should just do that.
> >> [...]
> >>
> >>> diff --git a/arch/mips/mach-ath79/ar933x/lowlevel_init.S
> >>> b/arch/mips/mach-ath79/ar933x/lowlevel_init.S new file mode 100644
> >>> index 0000000..72509ca
> >>> --- /dev/null
> >>> +++ b/arch/mips/mach-ath79/ar933x/lowlevel_init.S
> >>
> >> lowlevel_init.S should be C code too, I don't see anything which would
> >> require this to be ASM .
> >
> > I don't find SRAM in this chip, we need DDR memory to handle C runtime
> > statck.
>
> currently lowlevel_init() must be coded in assembly because it runs
> before RAM and caches are initialized. This function only exists to do
> that initialization. MIPS did this from the beginning. Maybe I will send
> some patches to use locked cache lines, but that should not be a hard
> requirement for adding new SoC's. Actually all modern MIPS based SoC's
> have some type of SRAM or first-stage bootloaders, thus adding the cache
> line lock feature was not really necessary. I would accept the current
> patch for the initial merge.
I believe the AR9331 has SRAM , at least according to the datasheet I have.
We should therefore use it.
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-12-26 17:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1451069788-6786-1-git-send-email-wills.wang@live.com>
2015-12-25 18:56 ` [U-Boot] [PATCH v4 1/8] include: Add support for "do_div" macro Wills Wang
2015-12-26 7:24 ` Marek Vasut
2015-12-26 15:48 ` Wills Wang
2015-12-26 13:09 ` Daniel Schwierzeck
2015-12-26 16:54 ` Wills Wang
2015-12-25 18:56 ` [U-Boot] [PATCH v4 2/8] mips: implement to access the KSEG0/1 memory range in map_physmem Wills Wang
2015-12-26 7:25 ` Marek Vasut
2015-12-25 18:56 ` [U-Boot] [PATCH v4 3/8] mips: add base support for atheros ath79 based SOCs Wills Wang
2015-12-26 7:28 ` Marek Vasut
2015-12-26 16:17 ` Wills Wang
2015-12-26 17:01 ` Daniel Schwierzeck
2015-12-26 17:06 ` Marek Vasut [this message]
2015-12-27 9:37 ` Wills Wang
2015-12-25 18:56 ` [U-Boot] [PATCH v4 4/8] mips: ath79: add serial driver for ar933x SOC Wills Wang
2015-12-26 13:20 ` Daniel Schwierzeck
2015-12-26 16:54 ` Wills Wang
2015-12-26 17:19 ` Daniel Schwierzeck
2015-12-27 6:28 ` Wills Wang
2015-12-27 8:21 ` Thomas Chou
2015-12-27 13:07 ` Thomas Chou
2015-12-27 8:31 ` Thomas Chou
2015-12-25 18:56 ` [U-Boot] [PATCH v4 5/8] mips: ath79: add spi driver Wills Wang
2015-12-26 13:23 ` Daniel Schwierzeck
2015-12-26 16:56 ` Wills Wang
2015-12-25 18:56 ` [U-Boot] [PATCH v4 6/8] mips: ath79: add AP121 reference board Wills Wang
2015-12-26 13:52 ` Daniel Schwierzeck
2015-12-26 16:59 ` Wills Wang
2015-12-26 17:07 ` Daniel Schwierzeck
2015-12-27 6:36 ` Wills Wang
2015-12-27 6:41 ` Marek Vasut
2015-12-27 7:03 ` Wills Wang
2015-12-27 7:10 ` Marek Vasut
2015-12-25 18:56 ` [U-Boot] [PATCH v4 7/8] mips: support optimize tuning for same common processor cores Wills Wang
2015-12-26 7:30 ` Marek Vasut
2015-12-26 18:58 ` Daniel Schwierzeck
2015-12-27 3:03 ` Wills Wang
2015-12-25 18:56 ` [U-Boot] [PATCH v4 8/8] mips: move optimize tuning option from deprecated config.mk to Kconfig Wills Wang
2015-12-26 7:30 ` Marek Vasut
2015-12-26 17:33 ` Wills Wang
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=201512261806.46935.marex@denx.de \
--to=marex@denx.de \
--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