From: Ralf Baechle <ralf@linux-mips.org>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: PNX8550 fails to compile in 2.6.17-rc4
Date: Sun, 11 Jun 2006 21:54:48 +0100 [thread overview]
Message-ID: <20060611205448.GA27193@linux-mips.org> (raw)
In-Reply-To: <acd2a5930606111321t11c29c77p83e56615b42902f9@mail.gmail.com>
On Mon, Jun 12, 2006 at 12:21:57AM +0400, Vitaly Wool wrote:
> On 6/7/06, Ralf Baechle <ralf@linux-mips.org> wrote:
> >This seems to be one of the serial bits for the ip3106 which must have
> >been lost on the way to kernel.org. Unfortunately the original author
> >does no longer take care of the code. I just took a stab at the PNX8550
> >code and it has a significant number of other problems. All small in
> >the sum large enough such that I will mark PNX8550 support broken.
>
> I took an attempt to compile 2.6.16.20 kernel from linux-mips.org for
> PNX8550 and it went a little further but also failed soon:
>
> CC arch/mips/philips/pnx8550/common/platform.o
> /home/vital/work/opensource/linux-
> 2.6.16.20/arch/mips/philips/pnx8550/common/platform.c:101: error: variable
> `pnx8550_usb_ohci_device' has initializer but incomplete type
> /home/vital/work/opensource/linux-
> 2.6.16.20/arch/mips/philips/pnx8550/common/platform.c:102: error: unknown
> field `name' specified in initializer
> /home/vital/work/opensource/linux-
> 2.6.16.20/arch/mips/philips/pnx8550/common/platform.c:102: warning: excess
> elements in struct initializer
> /home/vital/work/opensource/linux-
> 2.6.16.20/arch/mips/philips/pnx8550/common/platform.c:102: warning: (near
> initialization for `pnx8550_usb_ohci_device')
> /home/vital/work/opensource/linux-
> 2.6.16.20/arch/mips/philips/pnx8550/common/platform.c:103: error: unknown
> field `id' specified in initializer
> /home/vital/work/opensource/linux-
> 2.6.16.20/arch/mips/philips/pnx8550/common/platform.c:103: warning: excess
> elements in struct initializer
> ...
> /home/vital/work/opensource/linux-
> 2.6.16.20/arch/mips/philips/pnx8550/common/platform.c:101: error: storage
> size of `pnx8550_usb_ohci_device' isn't known
> /home/vital/work/opensource/linux-
> 2.6.16.20/arch/mips/philips/pnx8550/common/platform.c:112: error: storage
> size of `pnx8550_uart_device' isn't known
> make[2]: *** [arch/mips/philips/pnx8550/common/platform.o] Error 1
> make[1]: *** [arch/mips/philips/pnx8550/common] Error 2
> make: *** [vmlinux] Error 2
>
> Does it make sense to try to fix those? Or will it only result in more
> errore showing up next?
There is a whole number of small problems such as this one but as far
as I look at it all where only simple.
Ralf
prev parent reply other threads:[~2006-06-11 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 6:52 PNX8550 fails to compile in 2.6.17-rc4 Vitaly Wool
2006-06-07 14:27 ` Ralf Baechle
[not found] ` <01c201c68a47$1beaed90$7d01010a@p3>
2006-06-07 15:35 ` Ralf Baechle
[not found] ` <acd2a5930606111321t11c29c77p83e56615b42902f9@mail.gmail.com>
2006-06-11 20:54 ` Ralf Baechle [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=20060611205448.GA27193@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=vitalywool@gmail.com \
/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