public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@seznam.cz>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Microblaze: PULL request
Date: Sun, 5 Aug 2007 18:34:59 +0200	[thread overview]
Message-ID: <0a6b01c7d77e$905d8e50$0500a8c0@monstrone> (raw)
In-Reply-To: fa686aa40708050912u2484abaaiaaa7089d5eb84408@mail.gmail.com

Grant,


>> I thought please pull these changes to u-boot testing branch not to
>> mainline.
>
> Even patches pulled into testing need to be reviewed.  Wolfgang does
> merge testing into mainline periodically after all.
>
>> > 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 ++++++++++++++++++++++++++
>
> Heh, I even posted on that thread.  :)  Okay, I went back and took a
> look at this patch.  Mostly looks good, but I had a few comments.
> Take a read through and let me know what you think.

I know.

>
>>
>> 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.
>
> These patches I'm especially interested in.  I would like to review
> them before they are committed.

I know many developers needs these driver. For Microblaze I created 
configuration file. You can download it at www.monstr.eu
Emac is supported without DMA support. I plan to add support for simple and 
scatter gather DMA too.
I will wait for your review.

>> 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 +-
>
> Fair enough, but you should still post.
>
>> cmd_mfsl consist of only Microblaze dependent commands.
>> >>  common/cmd_mfsl.c                 |   11 +-
>
> ditto
>
>>
>>  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 +++++-
>
> Again, this stuff should hit the list before merging.  If there are no
> comments, then as microblaze custodian, you have discretion to add
> them to the microblaze tree and get them merged, but they should still
> hit the list *first* in case there are comments.

OK. I will be good guy. If you want I will send all changes to mailing list.
Microblaze changes are really cosmetic.

Michal Simek 

  reply	other threads:[~2007-08-05 16:34 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
2007-08-05 16:12     ` Grant Likely
2007-08-05 16:34       ` Michal Simek [this message]
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='0a6b01c7d77e$905d8e50$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