On 25/12/2013 02:07, Cyril Brulebois wrote:
-Suggests: firmware-linux
+Suggests: firmware-linux [linux-any], kfreebsd-downloader ( 11~)
[kfreebsd-any] | kfreebsd-downloader-10 [kfreebsd-any]
foo ( bar) is antique dpkg syntax.
I meant to say strictly greater (), though in this case it
Upstream part is merged in their repository now. I'm attaching an update for the
Debian part (regarding kfreebsd-downloader).
--
Robert Millan
diff -ur xserver-xorg-video-ati-7.2.0/debian/control xserver-xorg-video-ati-7.2.0.new/debian/control
--- xserver-xorg-video-ati-7.2.0/debian/control
Robert Millan r...@debian.org (2013-12-24):
Upstream part is merged in their repository now. I'm attaching an update for
the
Debian part (regarding kfreebsd-downloader).
--
Robert Millan
diff -ur xserver-xorg-video-ati-7.2.0/debian/control
Package: xserver-xorg-video-ati
Version: 7.2.0-1
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
Please consider this set of fixes for KMS support on kFreeBSD:
- Load radeonkms module instead of radeon.
- Replace linux-firmware with kfreebsd-downloader (non-free firmware).
reassign 732514 xserver-xorg-video-radeon
thanks
On 18/12/2013 13:31, Robert Millan wrote:
Package: xserver-xorg-video-ati
Version: 7.2.0-1
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
Please consider this set of fixes for KMS support on kFreeBSD:
- Load
On Wed, Dec 18, 2013 at 21:40:21 +0100, Robert Millan wrote:
- Load radeonkms module instead of radeon.
Actually, this was done at the wrong place. The first argument to
drmOpen() call is a red herring. It's supposed to load a kernel module,
but unless the module is already loaded this
On 18/12/2013 21:52, Julien Cristau wrote:
Does the freebsd kernel not autoload the driver?
No.
(Why not?)
Upstream doesn't provide a devd kldload ruleset for PCI devices, like they
do for USB. IIRC, this is because usage of PCI support internal interaces
in the driver codebase is less
On Wed, Dec 18, 2013 at 22:05:27 +0100, Robert Millan wrote:
Besides, when it comes to KMS drivers, is there a point in auto-loading them
just because the hardware is present? AFAICS it makes a lot more sense to load
them only when X is started and we know we will need them.
Yes. At least
On 18/12/2013 22:09, Julien Cristau wrote:
On Wed, Dec 18, 2013 at 22:05:27 +0100, Robert Millan wrote:
Besides, when it comes to KMS drivers, is there a point in auto-loading them
just because the hardware is present? AFAICS it makes a lot more sense to
load
them only when X is started
On Wed, Dec 18, 2013 at 4:09 PM, Julien Cristau jcris...@debian.org wrote:
On Wed, Dec 18, 2013 at 22:05:27 +0100, Robert Millan wrote:
Besides, when it comes to KMS drivers, is there a point in auto-loading them
just because the hardware is present? AFAICS it makes a lot more sense to
load
On Wed, Dec 18, 2013 at 4:18 PM, Robert Millan r...@debian.org wrote:
On 18/12/2013 22:09, Julien Cristau wrote:
On Wed, Dec 18, 2013 at 22:05:27 +0100, Robert Millan wrote:
Besides, when it comes to KMS drivers, is there a point in auto-loading them
just because the hardware is present?
11 matches
Mail list logo
