mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@linux.ie>
To: raven@themaw.net
Cc: Paul Jackson <pj@sgi.com>, Erdi Chen <erdi.chen@digeo.com>,
	davem@redhat.com, Andrew Morton <akpm@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sparc64 2.6.6-rc2-mm2 build busted: usb/core/hub.c hubstatus
Date: Wed, 28 Apr 2004 01:14:49 +0100 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0404280111430.2125@skynet> (raw)
In-Reply-To: <Pine.LNX.4.58.0404272234320.1547@donald.themaw.net>


> > >       CC [M]  drivers/char/drm/ffb_drv.o
> > >     In file included from drivers/char/drm/ffb_drv.c:336:
> > >     drivers/char/drm/drm_drv.h:547: error: `ffb_PCI_IDS' undeclared here (not in a function)
> > >     drivers/char/drm/drm_drv.h:547: error: initializer element is not constant
> > >     drivers/char/drm/drm_drv.h:547: error: (near initialization for `ffb_pciidlist[0]')
> > >     drivers/char/drm/ffb_drv.c:225: warning: `ffb_count_card_instances' defined but not used
> > >     make[3]: *** [drivers/char/drm/ffb_drv.o] Error 1

> It appears that for 2.6.6-rc2-mm2 this should be:
>
> #define ffb_PCI_IDS { 0,0,0 }
>
> which allows the kernel to build.

this should be fixed in the next pull from the DRM bk tree, bk seems to be
down so I can't confirm the fix is in there at the moment ...

Looking at the oops it looks like the framebuffer device is crashing, can
you trry building it without the ffb DRM and see if it still crashes?


Thanks,
Dave.

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person


  reply	other threads:[~2004-04-28  0:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27  3:49 Paul Jackson
2004-04-27  4:52 ` Ian Kent
2004-04-27 14:48   ` raven
2004-04-28  0:14     ` Dave Airlie [this message]
2004-04-28  2:29       ` Ian Kent
2004-04-28  2:27         ` Dave Airlie
2004-04-28 13:34           ` raven
2004-05-01 10:31             ` raven
2004-04-28  3:25       ` Randy.Dunlap
2004-04-28 20:22         ` Greg KH

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=Pine.LNX.4.58.0404280111430.2125@skynet \
    --to=airlied@linux.ie \
    --cc=akpm@osdl.org \
    --cc=davem@redhat.com \
    --cc=erdi.chen@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --cc=raven@themaw.net \
    /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

all inboxes | Powered by JetHome®