public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 0/7] add support for atheros ath79 based SOCs
Date: Thu, 21 Jan 2016 05:18:42 +0100	[thread overview]
Message-ID: <201601210518.42695.marex@denx.de> (raw)
In-Reply-To: <BLU436-SMTP170BF5C58B126BA912C0185FFC30@phx.gbl>

On Thursday, January 21, 2016 at 04:02:05 AM, Wills Wang wrote:
> On Thursday, January 21, 2016 09:32 AM, Marek Vasut wrote:
> > On Sunday, January 17, 2016 at 01:21:29 PM, Wills Wang wrote:
> >> On 01/17/2016 06:24 PM, Daniel Schwierzeck wrote:
> >>> 2016-01-17 6:49 GMT+01:00 Wills Wang <wills.wang@live.com>:
> >>>> On 01/17/2016 03:05 AM, Marek Vasut wrote:
> >>>>> On Saturday, January 16, 2016 at 07:13:46 PM, Wills Wang wrote:
> >>>>>> These series of patch add support for atheros ath79 based SOCs in
> >>>>>> u-boot, at the present moment it's just available for ar933x and
> >>>>>> qca953x chip.
> >>>>>> 
> >>>>>> This patch serises is based on mips_io_v4 branch on u-boot-mips
> >>>>>> repository
> >>>>>> [1] and tested on ar933x and qca953x board.
> >>>>>> 
> >>>>>> [1]
> >>>>>> 
> >>>>>> http://git.denx.de/?p=u-boot/u-boot-mips.git;a=shortlog;h=refs/heads
> >>>>>> /m ips_ io_v4
> >>>>> 
> >>>>> So if I didn't complain about this being sent as separate emails this
> >>>>> morning.
> >>>>> Please, do send your patches as a series, not as separate emails.
> >>>> 
> >>>> How to send a patch series by patman?
> >>> 
> >>> If your git-sendmail config is correctly set up, patman automatically
> >>> sends the cover letter and then all patches as response to that cover
> >>> letter.
> >>> 
> >>> You have to enable mail threading in git-sendmail. Check that with:
> >>> 
> >>> $ git config --get sendemail.thread
> >>> 
> >>> To enable it globally:
> >>> 
> >>> $ git config --global sendemail.thread true
> >> 
> >> Thanks, i will try it for the coming v8.
> > 
> > I got as far as booting my ar9330 rev 1 machine, though it did take
> > considerably amount of hackery. I also had to use locked cachelines for
> > stack, because it is far faster than using the SRAM on ar9331 . You can
> > find my hacks in the attachment, most of the stuff there is because
> > arduino yun is repugnant crappy piece of hardware and needs some extra
> > treatment.
> > 
> > You should mostly care about the hacks in start.S , in particular the one
> > setting bit 3 in CP0 in setup_c0_status seems important on mips 24kc
> > core. Daniel seems to have some ideas on this too I think, he helped me
> > finding out there's a problem.
> > 
> > Also, mips_cache_lock_24k does the job for locking the cachelines, but
> > (!) it is clearly a dirty hack. The start.S needs to be modularized in
> > some way for this to be properly integrat(ed|able).
> > 
> > In case I select SYS_MIPS_CACHE_INIT_RAM_LOAD , the machine hangs. No
> > idea why, but I suspect it makes no sense on a machine which has no
> > running DRAM anyway, so I removed this option.
> > 
> > Change to ddr.c seems correct, the values for DDR1 and DDR2 were swapped,
> > but I suggest you double-check it.
> > 
> > Ignore my AHB hack in lowlevel_init.S , it's necessary to keep my SPI NOR
> > running at low speed, since I am using an FPGA instead of real SPI NOR
> > and the FPGA implementation of the SPI NOR emulator cannot run at tens
> > of MHz.
> > 
> > I am now looking into implementing ethernet and USB support for ar9331,
> > did you look into it at all or not ? I'd like to avoid duplicating
> > efforts.
> 
> -#define CONFIG_SYS_TEXT_BASE            0x9f000000
> +#define CONFIG_SYS_TEXT_BASE            0xbf000000
> 
> Why need this change?

I believe this has no impact, it just prevents code from being cachable which
is convenient for me. You can ignore it.

  reply	other threads:[~2016-01-21  4:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 18:13 [U-Boot] [PATCH v7 0/7] add support for atheros ath79 based SOCs Wills Wang
2016-01-16 19:05 ` Marek Vasut
2016-01-17  5:49   ` Wills Wang
2016-01-17 10:24     ` Daniel Schwierzeck
2016-01-17 12:21       ` Wills Wang
2016-01-21  1:32         ` Marek Vasut
2016-01-21  2:58           ` Wills Wang
2016-01-21  5:35             ` Marek Vasut
2016-01-21  9:31               ` Wills Wang
2016-01-21 10:14                 ` Marek Vasut
2016-01-21  3:02           ` Wills Wang
2016-01-21  4:18             ` Marek Vasut [this message]
2016-01-26  5:28 ` Marek Vasut

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=201601210518.42695.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