All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] CPU PPC440x5 on Virtex5 FX
Date: Mon, 14 Jul 2008 10:11:15 +0200	[thread overview]
Message-ID: <200807141011.15777.sr@denx.de> (raw)
In-Reply-To: <aa76a2be0807131745p6e781eb1r451579a5cad5b8c9@mail.gmail.com>

Hi Racardo,

On Monday 14 July 2008, Ricardo Ribalda Delgado wrote:
>   I'm back from short hollydays, so expect some patches in this week
> :). Some general questions:
>
> master or next:
> Shall I apply the patches to master or to next? Both have
> modifications from 2 days ago.

"next" please. "master" is only for bug fixes now, since the merge window is 
closed.

> interrupts:
> I have been thinking about the irq handler and I am going to create this
> files:
>
>    -interrupt.c (actual file) -> common part
>    -uic.c (new file) -> uic part (extracted from interrupt.c)
>    -xilinx_iic.c (new file) -> Xilinx Irq handler

xilinx_iic.c ??? This really sounds like I2C. Please choose a different name.

> The Makefile will select among uic.c or xilinx_iic.c

Yes, this is possible. But IIRC then the microblaze CPU suport has the same or 
at least a similar interrupt handler. Isn't there a way to use some interrupt 
code on both CPU architectures?

> ml507:
> As you know I have been sending patches for the ml507 board. I will
> wait until this patch in accepted until I resend the ml507 patch. Is
> this ok?

To clarify: You will wait to send the ml507 board support patches until the 
CPU & interrupt stuff is accepted?

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
=====================================================================

  reply	other threads:[~2008-07-14  8:11 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
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 [this message]
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=200807141011.15777.sr@denx.de \
    --to=sr@denx.de \
    --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.