From: Angelos Manousarides <amanous@inaccessnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Patches for the PXA architecture
Date: Tue, 06 Jun 2006 20:07:23 +0300 [thread overview]
Message-ID: <4485B64B.6060105@inaccessnetworks.com> (raw)
I have a board with a PXA255 processor. This board has en external dual
uart chip and I want to support console setup on either the PXA uarts,
or one of the external uarts. I found the ns16550 driver which is quite
handy and configurable. It works quite well and supports the shifted
address bits to the external uart as well (PXA address pins 2-4 go to
uart 0-2).
There is a problem however with the compilation when using the external
uart. On the PXA uart driver (in cpu/pxa/serial.c) the code is included
always, there are no conditional like in the freescale processors. I
patched this file to isolate this code if one wants to use another uart.
The patch is attached. Using this config the object CONFIG_PXA_CONSOLE
(this can be renamed obviously if the developers don't find it
appropriate) has to be defined along with the CONFIG_BTUART,
CONFIG_FFUART and CONFIG_STUART.
Also attached is a patch for the davicom 9000 ethernet driver. When
debugging is enabled the driver will not compile.
Both patches are for u-boot 1.1.4. I know this is a user list, but I
don'y know what are the appropriate channels for bug fixes. I have added
two platforms (this one and a freescale one, based on MPC8275) to
u-boot, should I sumbit patched for them as well?
--
Angelos Manousarides
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uart.patch
Type: text/x-patch
Size: 472 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060606/c4d28b2b/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dm9000.patch
Type: text/x-patch
Size: 773 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060606/c4d28b2b/attachment-0001.bin
reply other threads:[~2006-06-06 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4485B64B.6060105@inaccessnetworks.com \
--to=amanous@inaccessnetworks.com \
--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