All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hellstrom <daniel@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/2] sparc32,leon: PCI patches
Date: Mon, 23 May 2011 08:49:36 +0000	[thread overview]
Message-ID: <4DDA1FA0.6080002@gaisler.com> (raw)
In-Reply-To: <4DB68838.1020304@gaisler.com>

David Miller wrote:

>From: Daniel Hellstrom <daniel@gaisler.com>
>Date: Fri, 20 May 2011 16:22:33 +0200
>
>  
>
>>I agree that it is a better solution in that case and in other cases
>>too. The problem will be for me to write a PCI Library in the limited
>>context of the PROM, it is much more complex that writing a PCI host
>>driver. The non-free PCI specification alone is heavy, compatibility
>>between PCI revisions and then there is the bridge
>>specification... ugg, I will probably have to leave that to the next
>>generation :)
>>    
>>
>
>I guess if it's really that bad we can merge your PCI changes for
>now, please resubmit them.
>  
>
Thanks, it means a lot to us.

>Julian:
>When I looked at this earlier, I was thinking that we might want to
>introduce a new KConfig variable, maybe CONFIG_LEON_PCI, to hide all
>this stuff behind so we don't have to do any complicated ifdefery or
>change any existing ifdefs.

I will add a PCIC and a LEON_PCI Kconfig option that depends on 
!LEON/LEON and PCI, as julian/sam suggests. I'm busy at the moment with 
other stuff it a pity these problem wasn't brought forward until now, is 
the merge window open until the end of the week?

Thanks,
Daniel

      parent reply	other threads:[~2011-05-23  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26  8:54 [PATCH 0/2] sparc32,leon: PCI patches Daniel Hellstrom
2011-05-16 20:01 ` David Miller
2011-05-19 13:13 ` Daniel Hellstrom
2011-05-19 19:01 ` David Miller
2011-05-20  8:01 ` Daniel Hellstrom
2011-05-20  8:08 ` David Miller
2011-05-20 14:22 ` Daniel Hellstrom
2011-05-20 18:24 ` David Miller
2011-05-23  8:49 ` Daniel Hellstrom [this message]

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=4DDA1FA0.6080002@gaisler.com \
    --to=daniel@gaisler.com \
    --cc=sparclinux@vger.kernel.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 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.