Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Sunil Amitkumar Janki" <devel.sjanki@gmail.com>
To: linux-mips@linux-mips.org
Subject: Re: 2.6.24-rc6 ssb build error
Date: Thu, 3 Jan 2008 17:29:21 +0100	[thread overview]
Message-ID: <767364c50801030829qd4e1be9g5f14d3d1814816d7@mail.gmail.com> (raw)
In-Reply-To: <767364c50801030815t1be0a58hd13af6a05b7ca3c5@mail.gmail.com>

On Jan 3, 2008 5:15 PM, Sunil Amitkumar Janki <devel.sjanki@gmail.com> wrote:
> I've built 2.6.24-rc6 for 32-bit MIPS and got the following error when
> building the ssb driver, probably because it has only been tested on
> x86. I will disable the driver for now and rebuild.
>

I forgot to include the error message:

ERROR: "pcibios_enable_device" [drivers/ssb/ssb.ko] undefined!
ERROR: "register_pci_controller" [drivers/ssb/ssb.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2

Regards,
Sunil

      reply	other threads:[~2008-01-03 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 16:15 2.6.24-rc6 ssb build error Sunil Amitkumar Janki
2008-01-03 16:29 ` Sunil Amitkumar Janki [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=767364c50801030829qd4e1be9g5f14d3d1814816d7@mail.gmail.com \
    --to=devel.sjanki@gmail.com \
    --cc=linux-mips@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