mplayer-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Original]

Re: [MPlayer-users] ANNOUNCE: new ./configure script


To: mplayer-users@xxxxxxxxxxxxxx
Subject: Re: [MPlayer-users] ANNOUNCE: new ./configure script
From: Dirk Pritsch <dp-privat@xxxxxxx>
Date: Mon, 19 Nov 2001 15:11:00 +0100
In-reply-to: <20011119135152.A14404@gruik.home>
References: <20011119122035.C13277@gruik.home> <200111191215.OAA47768@thot.banki.hu> <20011119135152.A14404@gruik.home>
User-agent: Mutt/1.3.23i

Hi,

On Mon, Nov 19, 2001 at 01:51:52PM +0100, pl wrote:
> 
> On Mon, Nov 19, 2001 at 02:15:26PM +0200, Arpi wrote:
> [...]
> > > > > Use that as a workaround. Yet, if anybody knows of a reliable way to
> > > > > autodetect it: share'n'enjoy :)
> > > > 
> > > > /sbin/lspci?
> > > Ok, it didn't come to my mind but yes, it's a solution :)

At least in debian lspci is in the pciutils package (priority: optional),
which isn't installed on every box (and just installing only for mplayer's
configure?...  um... :/ )

IMHO you should use something common in all kernels, which doesn't
require to install additional software, and /proc would eventually be
the best choice. What about /proc/bus/pci/devices which gives you the
vendor id ? 

> > >   How do I know if fb support is enabled in kernel (I could lsmod but if
> > >   statically linked...) ?
> > i think it can be enabled by default, if headers (fbdev.h ???) available.
> 
> fb headers are always available in linux/fb.h provided your C install is
> OK.

With kernel 2.4:

root@xxxxxxxxx:~ #cat /proc/fb
0 ATY Mach64

root@xxxxxxxxx:~ #cat /proc/devices |grep fb
 29 fb

root@xxxxxxxxx:~ #cat /proc/ksyms |grep fbcon
c01c664c fbcon_redraw_bmove_R5b61728f
c01c6600 fbcon_redraw_clear_Rf98e0fc7
.
.
.

(Don't know about 2.2)


Cheers,

Dirk



[Prev in Thread] Current Thread [Next in Thread]