From: "Robert Deliën" <robert.delien@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] NXP Semiconductors PNX8550/PNX8535/PNX8536 SoC support added
Date: Mon, 4 Dec 2006 13:43:27 +0100 [thread overview]
Message-ID: <000e01c717a1$cbd95560$dfdd9182@code1.emi.philips.com> (raw)
Hi,
The patch attached adds support for the NXP Semiconductors (former Philips
Semiconductors) PNX8550 SoC to U-Boot. As a target, the SilverBox
development target (config_silverbox) has been added.
The PNX8550 SoC contains a PR4450 MIPS core, a Philips implementation of a
MIPS32 processor. This patch will work on later - MIPS 4KEc based - SoCs
such as the PNX8535 and PNX8836 too, but there's no specific configuration
for those available yet. Serious rework of the MIPS lowlevel code is
required for that. Therefore the PNX8550 and PNX8535 U-Boot does not run
cached, but it does run in the cached memory segment.
For proper MIPS32 cache support significant rework of start.S and cache.S is
needed. We opted not to do this at this time as that may break existing MIPS
based boards. It is our intention to submit MIPS32 architecture compliant
versions of these when the PNX8550/PNX8535 board support is in U-Boot. This
will also include proper MIPS exception handling, something sorely missing.
The PNX8550 and PNX8535 are SoCs that are part of the NXP Semiconductors
Nexperia product line. NXP sells over 6,000,000 of these SoCs annually. They
are used in high-end TV sets, set-top boxes and PVRs.
With kind regards,
Robert Deli?n.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pnx8550support.diff.gz
Type: application/octet-stream
Size: 13004 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20061204/e9922ec2/attachment.obj
reply other threads:[~2006-12-04 12:43 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='000e01c717a1$cbd95560$dfdd9182@code1.emi.philips.com' \
--to=robert.delien@nxp.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