All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@seznam.cz>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] CPU PPC440x5 on Virtex5 FX
Date: Fri, 11 Jul 2008 15:52:24 +0200	[thread overview]
Message-ID: <48776598.8050403@seznam.cz> (raw)
In-Reply-To: <200807111430.21562.sr@denx.de>

Hi Stefan,


>> Some days ago a sent to mailing list patch (currently is in) where I rename
>> CONFIG_XILINX_ML300 -> CONFIG_XILINX_405.
>>
>> I would like to see if you can use the same style for 440 ->
>> CONFIG_XILINX_440. I have no detail information about ppc440 but IMHO only
>> virtex5 fx (or whatever) support it -> make no sense to me use virtex5 in
>> name.
>>
>> SR: Do you agree with me?
> 
> Yes, renaming this to CONFIG_XILINX_440 is a good idea.

nice to hear.

>> There is big part of code relate with interrupt controller which is the
>> same with microblaze. This should be handled in the same way. Any
>> suggestion? (Do generic driver?)
> 
> Yes, I already mentioned in my review, that this code should go into a 
> separate file. If the microblaze implementation is the same or very similar 
> then please use the same code here and move to to a common directory. 
> Perhaps:
> 
> drivers/interrupt/xilinx.c ?
> 
> Comments?

1. use macros names which are in microblaze xparameters.h. These values are
generate by u-boot BSP. Add ppc440 to it solves your problem with generic boards.
2. I don't know if is good idea to create drivers for interrupt controllers.
If yes xilinx_intc.c, will be better.
I will wait for WD comments.

>>
>> BTW: some comments in code.
> 
> Michal, your comments are very hard to spot since you don't quote the original 
> code by "> ".

I used web based email which is ...

Michal

> Best regards,
> Stefan
> 
> =====================================================================
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
> =====================================================================
> 

  parent reply	other threads:[~2008-07-11 13:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 11:35 [U-Boot-Users] [PATCH] CPU PPC440x5 on Virtex5 FX Ricardo Ribalda Delgado
2008-07-11 12:09 ` Michal Simek
2008-07-11 12:30   ` Stefan Roese
2008-07-11 12:35     ` Ricardo Ribalda Delgado
2008-07-11 13:52     ` Michal Simek [this message]
2008-07-11 15:03       ` Wolfgang Denk
2008-07-11 15:10         ` Stefan Roese
2008-07-11 19:35           ` Michal Simek
2008-07-14 11:46       ` Ricardo Ribalda Delgado
2008-07-14 12:06         ` Michal Simek
2008-07-11 12:33   ` Ricardo Ribalda Delgado
2008-07-11 12:22 ` Stefan Roese
2008-07-11 12:36   ` Ricardo Ribalda Delgado
2008-07-14  0:45   ` Ricardo Ribalda Delgado
2008-07-14  8:11     ` Stefan Roese
2008-07-14 10:12       ` Ricardo Ribalda Delgado
2008-07-14 12:06         ` Wolfgang Denk
2008-07-14 12:11           ` Michal Simek
2008-07-14 13:12             ` Ricardo Ribalda Delgado
  -- strict thread matches above, loose matches on Subject: below --
2008-07-14 17:03 Ricardo Ribalda Delgado
2008-07-14 17:03 ` Ricardo Ribalda Delgado
2008-07-14 17:06   ` Ricardo Ribalda Delgado

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=48776598.8050403@seznam.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.