From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] serial: 16550: Add JZ47xx support
Date: Thu, 26 May 2016 20:22:29 +0200 [thread overview]
Message-ID: <57473EE5.3080804@denx.de> (raw)
In-Reply-To: <20160526135524.GC26789@NP-P-BURTON>
On 05/26/2016 03:55 PM, Paul Burton wrote:
> On Thu, May 26, 2016 at 02:05:07PM +0200, Marek Vasut wrote:
>>> Interesting :) May I ask which platform/SoC you're working with? Have
>>> you seen the (unfortunately currently out of tree) port we did for the
>>> JZ4780-based Ci20? I recall the pain of squeezing SPL down to a small
>>> enough size well...
>>
>> I bought the CI20, yeah. I started with that tree and am now getting it
>> into mainline shape. I actually managed to optimize the SPL, so it does
>> not overflow. One of the things which helped a lot was removing slop[1]
>> from the structures and using appropriate data types in them (like don't
>> use u32 to store an 8bit number). I also tinified the MMC stack, so that
>> it won't pull in too much useless code.
>>
>> At this point, I have a u-boot running from SD card and the SD driver in
>> full U-Boot is already probing from DT and using DM. I sent Daniel the
>> updated patches, but they are still work in progress. Nonetheless, if
>> you want me forward that to you as well, let me know.
>>
>> I plan to get this CI20 submitted at some point this or next week, so it
>> can land in 2016.07 (I hope!) and then debian and fedora-mips (and other
>> distros) can pick it up and package proper. That's how I see it.
>
> That sounds great :) I'd be interested in seeing them but probably won't
> have any time to look at them for a few weeks anyway (busy with other
> work things & then getting married & going off on honeymoon!). So
> hopefully by the time I'd get round to having a look they'll be in
> mainline :)
Congratulations ! I sent you a separate mail and I'm going to submit
some of the stuff now too.
>> btw. what is the linux support status of the ci20 ? Is anyone working
>> on that? I saw the DTS in Linux, but it's pretty bare-bones.
>
> Yeah the support in mainline Linux is a bit basic at the moment. The
> biggest holdup is pinctrl support which I need to do some work on - the
> DT bindings are more complicated than they need to be, and the driver
> should probably be made more generic to cover other Ingenic SoCs before
> it goes into mainline.
I wonder if I should drill into that now ;-)
>> btw2. can I get the ci40 anywhere or is that just unobtainium board ?
>
> I'll email you separately about that.
>
> Thanks,
> Paul
>
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2016-05-26 18:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 0:19 [U-Boot] [PATCH] serial: 16550: Add JZ47xx support Marek Vasut
2016-05-25 22:17 ` Daniel Schwierzeck
2016-05-25 22:21 ` Marek Vasut
2016-05-25 22:31 ` Daniel Schwierzeck
2016-05-25 22:35 ` Marek Vasut
2016-05-26 13:29 ` Simon Glass
2016-05-26 16:34 ` Marek Vasut
2016-05-26 16:44 ` Simon Glass
2016-05-26 16:47 ` Marek Vasut
2016-05-26 16:48 ` Simon Glass
2016-05-26 16:53 ` Marek Vasut
2016-05-26 17:07 ` Simon Glass
2016-05-26 17:35 ` Marek Vasut
2016-05-26 17:47 ` Simon Glass
2016-05-26 17:01 ` Marek Vasut
2016-05-26 11:46 ` Paul Burton
2016-05-26 12:05 ` Marek Vasut
2016-05-26 13:55 ` Paul Burton
2016-05-26 18:22 ` 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=57473EE5.3080804@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