Re: Patched Xfree86 4.3.0 in Debian

[Aivils <ai...@un...>]

On Tuesday 11 May 2004 23:18, Kjetil Kjernsmo wrote:
> Hi all!
> 
> Long time, no see! Seems to have been quiet around here lately...?
> 
> Well, I bring some good news (and I need a little advice): Some of you
> might allready know, thanks to some great work by Andreas Schuldei and
> others, the patches to X most of us need to run multi-head setups have
> been applied to the Debian packages, they have been in the unstable
> release for 11 days now, and today, they are going into Sarge. Unless
> it breaks the system of somebody who aren't using it, it will be in
> Sarge when it some day is released as Stable! Which means, it will be
> accessible to many more users. Cool, eh? The first version it can be
> found in is 4.3.0.dfsg.1-1.
> 
> There has been some changes to the patch however. It has been reviewed
> by Branden Robinson in particular and the rest of the Debian X Strike
> Force team. Branden felt that "PrefBusID" wasn't very descriptive of
> what it really does, so it is in Debian known as "IsolateDevice". They
> have also written some documentation to it and made some other minor
> changes if I understand it correctly. In addition to "IsolateDevice",
> it also has a "SingleCard" layout option.
> 
> If I have understood the branches in the repository, the diff is
> available at
> http://necrotic.deadbeast.net/xsf/XFree86/branches-4.3.0-sid/debian/patches/080_pci_isolate_device_feature.diff
> and I thought you guys might want to review it.
> 
> I haven't tried the new packages out myself yet, I plan to do it Real
> Soon Now[tm]. But before I venture off into the somewhat unknown, I
> just wanted to ask those who understand the patch: To reconfigure my X
> servers to use the new Debian packages, all I have to do is
> s/PrefBusID/IsolateDevice/g
> right?

Yep.

> Then, I wondered about the HOWTO: Probably, we should now add some
> Debian-specific notes, now that people most likely can just use Sarge
> or Sid and get the X servers they need, but must use slightly different
> options than the rest of the world.

If end-user will start muptiple local xf86, then "IsolateDevice" is not
enough. Each xf86 open /dev/ttyXX , which one current is allowed under
Linus-tree kernel. Secondary xf86 become active when user press
Alt-F8 and primary xf86 goes spleep until user activate /dev/tty7.

Multiple current /dev/ttyXX exist only in linux-ruby.

> Unless you guys find Branden's 
> changes reasonable, and adopt and recommend the above patch to others
> that want to get this stuff running, in which case the HOWTO could be
> changed to reflect the new names. So, what do you think about that?

While single current TTY only allowed Branden have not a raw material
about what write how-to.

Aivils