mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bryce Harrington <bryce@canonical.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Justin Madru <jdm64@gawab.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]
Date: Tue, 18 Mar 2008 14:14:50 -0700	[thread overview]
Message-ID: <20080318211450.GU7206@bryceharrington.org> (raw)
In-Reply-To: <200803181300.39857.jbarnes@virtuousgeek.org>

On Tue, Mar 18, 2008 at 01:00:39PM -0700, Jesse Barnes wrote:
> > I could get it to build by ifdefing out th pci_device_map_range call,
> > and then adding -lpciaccess to the linker, however it segfaults without
> > that call.
> >
> > Does LIBPCIACCESS require xserver 1.4?  (We have 1.3 in Hardy).
(Obviously I meant 1.5 / 1.4 above.  Dah.)

> No, libpciaccess should be standalone, but the Intel driver requires 0.10 or 
> better... Which version are you building against?

I've put in a sync request for this to get updated for hardy.  (It still
will only be in universe, so won't be built automatically with -intel,
but at least users will be able to more easily compile it by hand.)

Meanwhile, here is a Ubuntu Hardy build of Debian's package:

  http://people.ubuntu.com/~bryce/Testing/libpciaccess/libpciaccess-dev_0.10-1_i386.deb
  http://people.ubuntu.com/~bryce/Testing/libpciaccess/libpciaccess0_0.10-1_i386.deb

Bryce


  parent reply	other threads:[~2008-03-19 21:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 19:02 Justin Madru
2008-03-12 19:36 ` Jesse Barnes
     [not found]   ` <47D8BF6A.9020905@gawab.com>
2008-03-13 17:09     ` Jesse Barnes
2008-03-14  4:22       ` Justin Madru
2008-03-14 17:29         ` Jesse Barnes
2008-03-15  3:48           ` Justin Madru
2008-03-15 17:35             ` Jesse Barnes
2008-03-15 18:16               ` Bryce Harrington
2008-03-17  1:28               ` Justin Madru
2008-03-18 19:07                 ` Bryce Harrington
2008-03-18 20:00                   ` Jesse Barnes
2008-03-18 20:53                     ` Bryce Harrington
2008-03-18 21:14                     ` Bryce Harrington [this message]
2008-03-18 21:17                       ` Jesse Barnes
2008-03-19 23:38                         ` Justin Madru
2008-03-19 23:48                           ` Jesse Barnes
2008-03-20  2:00                             ` Bryce Harrington
2008-03-25  3:07                             ` Justin Madru
2008-03-25 20:08                               ` Jesse Barnes
2008-03-26 18:32                                 ` Justin Madru
2008-03-31 19:24                                 ` Justin Madru
2008-04-01 20:22                                   ` Jesse Barnes
2008-04-09  4:56                                     ` Justin Madru
2008-04-09 15:24                                       ` Jesse Barnes
2008-04-14  3:46                                         ` Justin Madru

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=20080318211450.GU7206@bryceharrington.org \
    --to=bryce@canonical.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jdm64@gawab.com \
    --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
Powered by JetHome