From: Michal Simek <monstr@seznam.cz>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Microblaze: PULL request
Date: Sun, 5 Aug 2007 17:13:15 +0200 [thread overview]
Message-ID: <09ef01c7d773$283ff700$0500a8c0@monstrone> (raw)
In-Reply-To: fa686aa40708050747y2cc5b32eq69476876a76e1f36@mail.gmail.com
Hi Grant,
I thought please pull these changes to u-boot testing branch not to
mainline.
> I don't think I've seen any of these changes posted on the list for
> review. They need to be reviewed before being merged into mainline.
> Especially considering that some of the changes touch common code (not
> just microblaze).
These files were send in ROMFS patch 23.June 07
>> common/cmd_jffs2.c | 52 ++++--
>> fs/Makefile | 2 +-
>> fs/romfs/Makefile | 49 +++++
>> fs/romfs/romfs.c | 270 ++++++++++++++++++++++++++
New files for supporting EMAC and EMACLITE interface. Old support files are
in repository too.
I want to remove xilinx large files from U-Boot source tree. Emac driver use
PPC405 core too (ml300 board).
I tested it for Microblaze CPU and you can test it for PPC405 and give me a
respond.
We were talking about at the end of March.
>> Makefile | 9 +-
>> drivers/net/Makefile | 45 +++++
>> drivers/net/xilinx_emac.c | 372
>> ++++++++++++++++++++++++++++++++++++
>> drivers/net/xilinx_emac.h | 128 +++++++++++++
>> drivers/net/xilinx_emaclite.c | 378
>> +++++++++++++++++++++++++++++++++++++
Little name changes - because xuartlite serial interface isn't only one
which can be use with Microblaze CPU.
I think that can be helpful for PPC405 embedded core too that can use
uartlite serial interface.
>> drivers/serial_xuartlite.c | 2 +-
cmd_mfsl consist of only Microblaze dependent commands.
>> common/cmd_mfsl.c | 11 +-
Microblaze dependent files
>> cpu/microblaze/cache.c | 2 +-
>> cpu/microblaze/start.S | 6 +-
>> cpu/microblaze/timer.c | 7 +
>> lib_microblaze/time.c | 8 +
>> board/xilinx/xupv2p/Makefile | 21 +--
>> board/xilinx/xupv2p/config.mk | 6 +-
>> board/xilinx/xupv2p/xparameters.h | 27 ++--
>> include/configs/ml401.h | 1 +
>> include/configs/suzaku.h | 3 +
>> include/configs/xupv2p.h | 58 +++++-
Best regards,
Michal Simek
next prev parent reply other threads:[~2007-08-05 15:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 13:38 [U-Boot-Users] Microblaze: PULL request Michal Simek
2007-08-05 14:47 ` Grant Likely
2007-08-05 14:52 ` Grant Likely
2007-08-05 15:13 ` Michal Simek [this message]
2007-08-05 16:12 ` Grant Likely
2007-08-05 16:34 ` Michal Simek
2007-08-05 18:56 ` [U-Boot-Users] [PATCH 1/4] emac Michal Simek
2007-08-05 20:07 ` Wolfgang Denk
2007-08-06 20:11 ` Michal Simek
2007-08-05 22:28 ` Grant Likely
2007-08-05 18:56 ` [U-Boot-Users] [PATCH 2/4] emaclite Michal Simek
2007-08-05 20:05 ` Wolfgang Denk
2007-08-06 20:00 ` Michal Simek
2007-08-06 20:54 ` Wolfgang Denk
2007-08-05 18:56 ` [U-Boot-Users] [PATCH 3/4] microblaze changes Michal Simek
2007-08-05 20:08 ` Wolfgang Denk
2007-08-05 18:56 ` [U-Boot-Users] [PATCH 4/4] romfs Michal Simek
2007-08-05 20:38 ` Wolfgang Denk
2007-08-05 20:01 ` [U-Boot-Users] Microblaze: PULL request Wolfgang Denk
2007-08-05 22:25 ` Grant Likely
2007-08-05 22:27 ` Wolfgang Denk
2007-08-05 22:32 ` Grant Likely
2007-08-06 17:03 ` Michal Simek
2007-08-05 19:59 ` Wolfgang Denk
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='09ef01c7d773$283ff700$0500a8c0@monstrone' \
--to=monstr@seznam.cz \
--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