public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Adrian Bunk <bunk@kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: mips BCM47XX compile error
Date: Sun, 25 May 2008 13:48:51 +0200	[thread overview]
Message-ID: <200805251348.52010.mb@bu3sch.de> (raw)
In-Reply-To: <20080525113634.GB20502@hall.aurel32.net>

On Sunday 25 May 2008 13:36:34 Aurelien Jarno wrote:
> On Sun, May 25, 2008 at 11:53:46AM +0200, Michael Buesch wrote:
> > On Monday 21 April 2008 09:28:51 Aurelien Jarno wrote:
> > > On Mon, Apr 21, 2008 at 12:49:42AM +0200, Aurelien Jarno wrote:
> > > > Michael Buesch a écrit :
> > > > > On Sunday 20 April 2008 12:03:47 Adrian Bunk wrote:
> > > > >> Commit aab547ce0d1493d400b6468c521a0137cd8c1edf
> > > > >> (ssb: Add Gigabit Ethernet driver) causes the following
> > > > >> build error with bcm47xx_defconfig:
> > > > >>
> > > > >> <--  snip  -->
> > > > >>
> > > > >> ...
> > > > >>   LD      .tmp_vmlinux1
> > > > >> arch/mips/pci/built-in.o: In function `pcibios_enable_device':
> > > > >> (.text+0x1f8): undefined reference to `pcibios_plat_dev_init'
> > > > >> arch/mips/pci/built-in.o: In function `pcibios_enable_device':
> > > > >> (.text+0x1f8): relocation truncated to fit: R_MIPS_26 against `pcibios_plat_dev_init'
> > > > >> arch/mips/pci/built-in.o: In function `pcibios_init':
> > > > >> pci.c:(.init.text+0x14c): undefined reference to `pcibios_map_irq'
> > > > >> pci.c:(.init.text+0x158): undefined reference to `pcibios_map_irq'
> > > > >> make[1]: *** [.tmp_vmlinux1] Error 1
> > > > > 
> > > > > Some parts of the new 47xx arch code are not ported, yet.
> > > > 
> > > > It would have been nice at least to warn before breaking a platform.
> > > > 
> > > > > Somebody should port all the new code from openwrt SVN over to mainline.
> > > > > I don't really have time for that, at the moment, though.
> > > > 
> > > > I gave a quick look at openwrt SVN, and only find 2.6.23 patches. I
> > > > can't find a possible fix among them. Do you have a better pointer?
> > > > 
> > > 
> > > I have finally found it, the code was not in a form of a patch, but in
> > > form of a C code file.
> > > 
> > > I am working on a fix.
> > > 
> > 
> > What is the status of the fix?
> > We have a bugzilla entry
> > http://bugzilla.kernel.org/show_bug.cgi?id=10493
> > So if it's not ready, yet, I will have to fix it by myself.
> > 
> 
> A patch [1] has been sent 1 month ago, it waits with the other BCM47xx
> patches.
> 
> Aurelien
> 
> [1] http://marc.info/?l=linux-kernel&m=120876451216558&w=2
> 

Thanks a lot, Aurelien :)


-- 
Greetings Michael.

  reply	other threads:[~2008-05-25 11:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20 10:03 mips BCM47XX compile error Adrian Bunk
2008-04-20 10:14 ` Michael Buesch
2008-04-20 22:49   ` Aurelien Jarno
2008-04-21  7:28     ` Aurelien Jarno
2008-05-25  9:53       ` Michael Buesch
2008-05-25 11:36         ` Aurelien Jarno
2008-05-25 11:48           ` Michael Buesch [this message]
2008-04-21 13:48     ` Michael Buesch

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=200805251348.52010.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=aurelien@aurel32.net \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linville@tuxdriver.com \
    --cc=ralf@linux-mips.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