linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 3/5] [FS_ENET] OF-related fixup for FEC and SCC MAC's
Date: Mon, 22 Jan 2007 17:04:53 +0300	[thread overview]
Message-ID: <20070122170453.1fee7c74@localhost.localdomain> (raw)
In-Reply-To: <17844.36037.859630.386937@cargo.ozlabs.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

On Mon, 22 Jan 2007 21:07:01 +1100
Paul Mackerras wrote:

> Vitaly Bordug writes:
> 
> > +#ifndef CONFIG_PPC_MERGE
> >  	FW(fecp, ivec, (fep->interrupt / 2) << 29);
> > -	
> > +#else
> > +	FW(fecp, ivec, (irq_map[fep->interrupt].hwirq / 2) << 29);
> > +#endif
> 
> This would be much cleaner if you use virq_to_hw() and add a
> definition of virq_to_hw to the asm-ppc headers, so that you can avoid
> putting ifdefs in code.
> 
Well, first of all it is netdev stuff(as being in drivers/net) and here for reference only. virq_to_hw approach seems very interesting though...

> Also, it seems a bit bogus to be using the hardware interrupt number
> directly here.
> 
FEC is sort of external and requires such a surgery iirc

> Is it just 82xx that uses this driver, or do other chips (85xx?) use
> it too?
>
It exists on 8560ads (and alike) and mpc8xx (mostly). mpc82xx usually is featuring FCC.
 
--
Thanks, Vitaly

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-01-22 14:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13  0:41 [PATCH 1/5] [POWERPC] cpm2: CPM2 interrupt controller fix Vitaly Bordug
2007-01-13  0:42 ` [PATCH 2/5] [POWERPC] cpm_uart: OF-related fix for arch/powerpc Vitaly Bordug
2007-01-22 10:02   ` Paul Mackerras
2007-01-22 13:55     ` Vitaly Bordug
2007-01-13  0:42 ` [PATCH 3/5] [FS_ENET] OF-related fixup for FEC and SCC MAC's Vitaly Bordug
2007-01-22 10:07   ` Paul Mackerras
2007-01-22 14:04     ` Vitaly Bordug [this message]
2007-01-13  0:42 ` [PATCH 4/5] [POWERPC] Fix kernel build errors for mpc8272ads and mpc8560ads Vitaly Bordug
2007-01-13  0:42 ` [PATCH 5/5] [POWERPC] mpc8272ads: defconfig Vitaly Bordug
2007-01-22  9:57 ` [PATCH 1/5] [POWERPC] cpm2: CPM2 interrupt controller fix Paul Mackerras
2007-01-22 13:43   ` Vitaly Bordug
2007-01-22 19:55     ` Benjamin Herrenschmidt
2007-01-22 20:55       ` Vitaly Bordug
2007-01-22 21:13         ` Benjamin Herrenschmidt
2007-01-22 21:42           ` Vitaly Bordug
2007-01-24 10:07             ` Paul Mackerras
2007-01-24 13:05               ` Vitaly Bordug

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=20070122170453.1fee7c74@localhost.localdomain \
    --to=vbordug@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /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;
as well as URLs for NNTP newsgroup(s).