From: Stephan Linz <linz@li-pro.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] microblaze: usable uart16550 for big endian systems
Date: Thu, 24 Nov 2011 21:30:02 +0100 [thread overview]
Message-ID: <1322166602.3870.212.camel@keto> (raw)
In-Reply-To: <4ECE9771.7080403@monstr.eu>
Am Donnerstag, den 24.11.2011, 20:13 +0100 schrieb Michal Simek:
> Stephan Linz wrote:
> >--snip--
> >>
> >> Here is patch I have used. Please add that changes to v2 patch.
> >
> > I'll do it this way. Give me a little time to change and test it.
> > Currently I am sill working on refactoring of the LL TEMAC driver. I
> > hope, the refactored driver than can merge in mainline ...
>
> I have done it some time ago and look at "[PATCH v3] net: ll_temac:
> Add LL TEMAC driver to u-boot thread".
Hi Michal,
yes, I've read the whole thread.
> I have attached the latest version I have and I am not going to change
> it to follow "new" u-boot network driver style
Hm, but it is possible ...
> because I would like to keep ppc dcr support.
Even this was the main work I've done last week. I've split the driver
code into differnt sub modules (xilinx_ll_temac_fifo and
xilinx_ll_temac_sdram), introduce some call back functions into the sub
modules to harmonize the main driver code and divide the sdma code into
the two different bus access methodes: direct 32 bit memory access
(Microblaze) and indirect access via DCR (Xilinx PPC4xx).
Please, give me some time to finish the refactoring. I'll release all
results as fast as possible her in U-Boot list.
But, one issue was uncleare to me. Some functions, for example
xps_ll_temac_hostif_set(), were prepared to set bit 10 of CTL register.
But CTL bit 10 is not defined by any LL TEMAC documentation. Why did you
done this?
Thanks,
Stephan
>
> Thanks,
> Michal
>
> --
> Michal Simek, Ing. (M.Eng)
> w: www.monstr.eu p: +42-0-721842854
> Maintainer of Linux kernel 2.6 Microblaze Linux -
> http://www.monstr.eu/fdt/
> Microblaze U-BOOT custodian
--
Viele Gr??e,
Stephan Linz
______________________________________________________________________________
MB-Ref: http://www.li-pro.de/xilinx_mb:mbref:start
OpenDCC: http://www.li-pro.net/opendcc.phtml
PC/M: http://www.li-pro.net/pcm.phtml
Sourceforge: http://sourceforge.net/users/slz
Gitorious: https://gitorious.org/~slz
next prev parent reply other threads:[~2011-11-24 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 12:03 [U-Boot] [PATCH] microblaze: usable uart16550 for big endian systems Stephan Linz
2011-11-21 7:21 ` Michal Simek
2011-11-21 18:18 ` Stephan Linz
2011-11-23 14:40 ` Michal Simek
2011-11-24 18:29 ` Stephan Linz
2011-11-24 19:13 ` Michal Simek
2011-11-24 20:30 ` Stephan Linz [this message]
2011-11-25 10:28 ` Michal Simek
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=1322166602.3870.212.camel@keto \
--to=linz@li-pro.net \
--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