Bug 20742 - [patch] xorg.conf man page - 'Device' no longer mandatory
Summary: [patch] xorg.conf man page - 'Device' no longer mandatory
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.3 (2007.09)
Hardware: All Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
Keywords: patch
Depends on:
Reported: 2009-03-18 21:10 UTC by Bryce Harrington
Modified: 2013-02-15 08:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

0001-X-boots-up-without-a-Device-identifier-don-t-need.patch (853 bytes, patch)
2009-03-18 21:10 UTC, Bryce Harrington
no flags Details | Splinter Review
man_device_not_mandatory.patch (1.28 KB, patch)
2013-02-08 21:31 UTC, Bryce Harrington
no flags Details | Splinter Review
xorg.conf (150 bytes, text/plain)
2013-02-08 23:20 UTC, Bryce Harrington
no flags Details
Xorg.0.log (34.05 KB, text/plain)
2013-02-08 23:21 UTC, Bryce Harrington
no flags Details

Description Bryce Harrington 2009-03-18 21:10:42 UTC
Created attachment 24027 [details] [review]

man xorg.conf states that the 'Device' identifier is required in the 'Screen' section, yet in reality X will default properly without it.  Attached patch updates man page.

c.f. https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/261577
Comment 1 Corbin Simpson 2010-03-27 12:25:41 UTC
Tagging patch; will triage later.
Comment 2 Bryce Harrington 2013-02-08 21:31:45 UTC
Created attachment 74452 [details] [review]

Here's a more thorough patch.  This removes one more mention of the mandatoriness of this optional parameter.
Comment 3 Bryce Harrington 2013-02-08 23:20:44 UTC
Created attachment 74454 [details]

xorg.conf test case used to verify
Comment 4 Bryce Harrington 2013-02-08 23:21:08 UTC
Created attachment 74455 [details]

Log from verification
Comment 5 Timo Aaltonen 2013-02-15 08:30:24 UTC
this is now fixed in master

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.