From: Chris Zankel <chris@zankel.net>
To: Adrian Bunk <bunk@kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] xtensa: don't offer PARPORT_PC
Date: Mon, 14 Apr 2008 16:00:48 -0700 [thread overview]
Message-ID: <4803E220.6030807@zankel.net> (raw)
In-Reply-To: <20080414221312.GI26885@cs181133002.pp.htv.fi>
Hi Adrian,
Most of the boards with Xtensa don't have PCI, and the PCI bridge on the
two boards I know have PCI are more or less broken. One (with a V3)
doesn't support byte/word accesses and the other one has broken
PCI-Master to main memory connection. I'll work on the one that has
only 32-bit access and will try to fix it.
Thanks,
-Chris
Adrian Bunk wrote:
> On Mon, Apr 14, 2008 at 10:31:24PM +0100, Alan Cox wrote:
>> On Mon, 14 Apr 2008 22:55:51 +0300
>> Adrian Bunk <bunk@kernel.org> wrote:
>>
>>> This patch fixes the following compile error:
>>>
>>> <-- snip -->
>>>
>>> ...
>>> CC [M] drivers/parport/parport_pc.o
>>> /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/parport/parport_pc.c:67:25: error: asm/parport.h: No such file or directory
>>> /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/parport/parport_pc.c: In function 'parport_pc_find_ports':
>>> /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/parport/parport_pc.c:3215: error: implicit declaration of function 'parport_pc_find_nonpci_ports'
>>> make[3]: *** [drivers/parport/parport_pc.o] Error 1
>>>
>>> <-- snip -->
>>>
>>> Signed-off-by: Adrian Bunk <bunk@kernel.org>
>> If xtensa has PCI then if you fix up the headers so the PCI stuff works
>> we'll be in a better shape.
>
> The only merged platform does not support PCI, and I don't have any
> xtensa hardware for knowing what to put there.
>
> Chris?
>
> cu
> Adrian
>
prev parent reply other threads:[~2008-04-14 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 19:55 [2.6 patch] xtensa: don't offer PARPORT_PC Adrian Bunk
2008-04-14 20:33 ` Rogan Dawes
2008-04-14 21:34 ` Alan Cox
2008-04-14 21:31 ` Alan Cox
2008-04-14 22:13 ` Adrian Bunk
2008-04-14 23:00 ` Chris Zankel [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=4803E220.6030807@zankel.net \
--to=chris@zankel.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox