From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [SoCFPGA] next steps
Date: Wed, 8 Oct 2014 21:05:26 +0200 [thread overview]
Message-ID: <201410082105.26318.marex@denx.de> (raw)
In-Reply-To: <54353992.8030906@opensource.altera.com>
On Wednesday, October 08, 2014 at 03:18:10 PM, Dinh Nguyen wrote:
> Hi Marek,
Hi all!
> On 10/7/14, 7:45 AM, Marek Vasut wrote:
> > Hey,
> >
> > given that we now have most of the u-boot socfpga stuff in mainline, I
> > decided it would be a good idea to list what we're still missing and we
> > should also decide how to move on now.
>
> Thanks for all of your hard work on this!
I only did what needed to be done and I'm looking forward to you taking over
shortly ;-)
[...]
> > SPL: This is something we still miss from mainline. We will need to
> > discuss
> >
> > this thoroughly, but one thing is obvious already -- we need to
> > figure out how to interoperate with Quartus resp. the bsp-editor
> > generated header files to assemble the SPL properly.
>
> Have you or anyone else already started on this work? If not, then this
> is an area that I can start to work on.
No, noone did and I'd be really happy if you took this one.
> > USB: This is scheduled for the next merge window. The DWC2 driver is
> > cleaned
> >
> > up and seems to be in rather good state. The USB driver currently
> > resides in [2]
> >
> > EPCQ: This is something I prepared and tested real quick. The EPCS/EPCQ
> > SPI NOR
> >
> > can be operated via the Altera SPI driver, which is currently
> > unused at all and thus suffering bitrot. The current cleanup is
> > here [3]
> >
> > NET: Does the SoCDK use EMAC0 or EMAC1 ? I believe we still have this
> > issue
> >
> > open, I recall Chin was complaining about this.
>
> The SoCDK is using EMAC1.
I guess we'd need one more quick patch for current mainline then, since this
seems to be broken ever since. I will bake one shortly.
Also, let me add two more goals:
- Migrate to driver model
- Support probing of the whole board from Device Tree Blob
This would make our lives so much easier, so we should aim for this. I don't
know if it is realistic to make this happen for 2015.01, but I would like to
keep this in mind.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-10-08 19:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 12:45 [U-Boot] [SoCFPGA] next steps Marek Vasut
2014-10-08 8:58 ` Michal Simek
2014-10-08 10:39 ` Marek Vasut
2014-10-08 11:17 ` Pavel Machek
2014-10-08 20:09 ` Tom Rini
2014-10-09 8:37 ` Michal Simek
2014-10-09 11:20 ` Jagan Teki
2014-10-09 13:42 ` Marek Vasut
2014-10-09 16:11 ` Jagan Teki
2014-10-09 16:15 ` [U-Boot] Discussion topics / issues Marek Vasut
2014-10-09 16:41 ` Jagan Teki
2014-10-09 14:03 ` Marek Vasut
2014-10-09 14:45 ` Michal Simek
2014-10-09 15:57 ` Tom Rini
2014-10-09 16:10 ` Marek Vasut
2014-10-09 16:25 ` Tom Rini
2014-10-09 16:29 ` Marek Vasut
2014-10-09 22:11 ` Pavel Machek
2014-10-09 22:24 ` Wolfgang Denk
2014-10-09 23:00 ` Pavel Machek
2014-10-10 12:22 ` Wolfgang Denk
2014-10-10 14:04 ` Jeroen Hofstee
2014-10-10 14:26 ` Marek Vasut
2014-10-10 14:35 ` Fabio Estevam
2014-10-10 16:09 ` Jeroen Hofstee
2014-10-10 19:51 ` Albert ARIBAUD
2014-10-10 20:40 ` Jeroen Hofstee
2014-10-10 21:13 ` Albert ARIBAUD
2014-10-11 15:03 ` Wolfgang Denk
2014-10-11 15:16 ` Wolfgang Denk
2014-10-15 8:40 ` [U-Boot] puts() and newlines (was Re: Discussion topics / issues) Pavel Machek
2014-10-15 9:42 ` Pavel Machek
2014-10-20 15:51 ` Tom Rini
2014-10-11 14:44 ` [U-Boot] Discussion topics / issues Wolfgang Denk
2014-10-12 15:06 ` Jeroen Hofstee
2014-10-09 23:05 ` Pavel Machek
2014-10-10 11:05 ` Albert ARIBAUD
2014-10-10 12:34 ` Wolfgang Denk
2014-10-10 0:12 ` Tom Rini
2014-10-08 13:18 ` [U-Boot] [SoCFPGA] next steps Dinh Nguyen
2014-10-08 19:05 ` Marek Vasut [this message]
2014-10-11 18:22 ` Masahiro YAMADA
2014-10-19 21:19 ` 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=201410082105.26318.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