Re: r18868 - in trunk/packages/ddetect: . debian
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 04 August 2004 22:10, Sven Luther wrote: On Wed, Aug 04, 2004 at 03:08:54PM -0400, Joey Hess wrote: Why should d-i care about the mouse? Shouldn't you be patching X's configuration program? Well, this is the modules which will be added to the /etc/modules. I understand that it may well be possible that the X installation stuff, but i suppose the mouse should be usefull even for gpm or other non-X stuff, and having no mouse driver module loaded after the reboot is not a nice thing. So, if this is not the right place for registering this module for future use, what is ? discover, which has trouble handling more than one module per pci id ? hotplug ? The X configuration stuff ? i have some doubt about Branden accepting this kind of stuff though, unless there is a generic module loading mechanism for X, and this doesn't solve the case of non-X mouse users. Could it be this is the same problem as #255744? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBF3grgm/Kwh6ICoQRAvLHAJ4pbozWFvc+gZOSzFeYquQf8fJpCACePkY8 eEX5GWtVyXmFwaC68lK1JcE= =azaL -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r18868 - in trunk/packages/ddetect: . debian
On Mon, Aug 09, 2004 at 03:12:02PM +0200, Frans Pop wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 04 August 2004 22:10, Sven Luther wrote: On Wed, Aug 04, 2004 at 03:08:54PM -0400, Joey Hess wrote: Why should d-i care about the mouse? Shouldn't you be patching X's configuration program? Well, this is the modules which will be added to the /etc/modules. I understand that it may well be possible that the X installation stuff, but i suppose the mouse should be usefull even for gpm or other non-X stuff, and having no mouse driver module loaded after the reboot is not a nice thing. So, if this is not the right place for registering this module for future use, what is ? discover, which has trouble handling more than one module per pci id ? hotplug ? The X configuration stuff ? i have some doubt about Branden accepting this kind of stuff though, unless there is a generic module loading mechanism for X, and this doesn't solve the case of non-X mouse users. Could it be this is the same problem as #255744? Indeed it sounds similar, except that we are on powerpc, and i am not sure enough about the whole hotplug thingy to be sure if the psmouse module will be loaded or not. Keep in mind that most powerpc folk usually use usb mouses, so X may maybe not try to load psmouse on powerpc, not sure. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r18868 - in trunk/packages/ddetect: . debian
On Mon, Aug 09, 2004 at 03:30:21PM -0400, Rick_Thomas wrote: On Mon, 2004-08-09 at 09:40, Sven Luther wrote: Indeed it sounds similar, except that we are on powerpc, and i am not sure enough about the whole hotplug thingy to be sure if the psmouse module will be loaded or not. Keep in mind that most powerpc folk usually use usb mouses, so X may maybe not try to load psmouse on powerpc, not sure. Don't forget us OldWorld Mac users who have ADB mice/keyboards! Sure. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r18868 - in trunk/packages/ddetect: . debian
On Mon, 2004-08-09 at 09:40, Sven Luther wrote: Indeed it sounds similar, except that we are on powerpc, and i am not sure enough about the whole hotplug thingy to be sure if the psmouse module will be loaded or not. Keep in mind that most powerpc folk usually use usb mouses, so X may maybe not try to load psmouse on powerpc, not sure. Don't forget us OldWorld Mac users who have ADB mice/keyboards! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r18868 - in trunk/packages/ddetect: . debian
On Wed, Aug 04, 2004 at 10:51:55PM +0100, Colin Watson wrote: On Wed, Aug 04, 2004 at 10:10:21PM +0200, Sven Luther wrote: On Wed, Aug 04, 2004 at 03:08:54PM -0400, Joey Hess wrote: Why should d-i care about the mouse? Shouldn't you be patching X's configuration program? Well, this is the modules which will be added to the /etc/modules. I understand that it may well be possible that the X installation stuff, but i suppose the mouse should be usefull even for gpm or other non-X stuff, and having no mouse driver module loaded after the reboot is not a nice thing. Notice that i asked about this (altough addressed to Kamion) on irc before making the change while you where there, so you could have remarqued on it before i go forward and implemented this. If you want to discuss a design decision, this mailing list would be far better than the transient and overfilled medium of IRC. Ok. Checking in code is obviously also a good way to get it discussed :). So, if this is not the right place for registering this module for future use, what is ? discover, which has trouble handling more than one module per pci id ? hotplug ? The X configuration stuff ? i have some doubt about Branden accepting this kind of stuff though, unless there is a generic module loading mechanism for X, and this doesn't solve the case of non-X mouse users. mdetect seems like clearly the right place. Its package description and its man page both suggest that gpm could easily be modified to use it (indeed, mdetect's default behaviour is to produce output suitable for configuring gpm). And is it part of base, and sure to be run if the user does a clean install and chose the X task in tasksel ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r18868 - in trunk/packages/ddetect: . debian
On Thu, Aug 05, 2004 at 02:51:42PM +0100, Colin Watson wrote: On Thu, Aug 05, 2004 at 11:16:31AM +0200, Sven Luther wrote: On Wed, Aug 04, 2004 at 10:51:55PM +0100, Colin Watson wrote: mdetect seems like clearly the right place. Its package description and its man page both suggest that gpm could easily be modified to use it (indeed, mdetect's default behaviour is to produce output suitable for configuring gpm). And is it part of base, and sure to be run if the user does a clean install and chose the X task in tasksel ? Yes, base-config installs mdetect and xserver-xfree86.config uses it (although you may have to request that it be used, I don't remember; in any case we'd be in the same position as other architectures here). Ok, i will look at it then. BTW, Hopefully Branden will be more responsive in updating the package than the discover folk. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r18868 - in trunk/packages/ddetect: . debian
Why should d-i care about the mouse? Shouldn't you be patching X's
configuration program?
Sven Luther wrote:
Author: luther
Date: Wed Aug 4 12:56:19 2004
New Revision: 18868
Modified:
trunk/packages/ddetect/debian/changelog
trunk/packages/ddetect/hw-detect.sh
Log:
Added psmouse module registration to powerpc chrp/prep subarches, or X will have no
pointer.
Modified: trunk/packages/ddetect/debian/changelog
==
--- trunk/packages/ddetect/debian/changelog (original)
+++ trunk/packages/ddetect/debian/changelog Wed Aug 4 12:56:19 2004
@@ -4,8 +4,11 @@
- Add more entries to devnames.txt.
- grep for ^${module}: to prevent e1000's description matching for
e100. (Closes: #262626)
+ * Sven Luther
+- Added support for loading the psmouse modules on powerpc/chrp
+ and prep too, since X is complaining after the reboot.
- -- Joshua Kwan [EMAIL PROTECTED] Sun, 1 Aug 2004 02:07:11 -0700
+ -- Sven Luther [EMAIL PROTECTED] Wed, 4 Aug 2004 20:52:39 +0200
ddetect (1.00) unstable; urgency=low
Modified: trunk/packages/ddetect/hw-detect.sh
==
--- trunk/packages/ddetect/hw-detect.sh (original)
+++ trunk/packages/ddetect/hw-detect.sh Wed Aug 4 12:56:19 2004
@@ -243,6 +243,9 @@
register-module i8042
echo atkbd:AT keyboard support
register-module atkbd
+ echo psmouse:AT mouse support
+ register-module psmouse
+ ;;
;;
esac
}
--
see shy jo
signature.asc
Description: Digital signature
Re: r18868 - in trunk/packages/ddetect: . debian
On Wed, Aug 04, 2004 at 03:08:54PM -0400, Joey Hess wrote: Why should d-i care about the mouse? Shouldn't you be patching X's configuration program? Well, this is the modules which will be added to the /etc/modules. I understand that it may well be possible that the X installation stuff, but i suppose the mouse should be usefull even for gpm or other non-X stuff, and having no mouse driver module loaded after the reboot is not a nice thing. Notice that i asked about this (altough addressed to Kamion) on irc before making the change while you where there, so you could have remarqued on it before i go forward and implemented this. So, if this is not the right place for registering this module for future use, what is ? discover, which has trouble handling more than one module per pci id ? hotplug ? The X configuration stuff ? i have some doubt about Branden accepting this kind of stuff though, unless there is a generic module loading mechanism for X, and this doesn't solve the case of non-X mouse users. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r18868 - in trunk/packages/ddetect: . debian
On Wed, Aug 04, 2004 at 10:10:21PM +0200, Sven Luther wrote: On Wed, Aug 04, 2004 at 03:08:54PM -0400, Joey Hess wrote: Why should d-i care about the mouse? Shouldn't you be patching X's configuration program? Well, this is the modules which will be added to the /etc/modules. I understand that it may well be possible that the X installation stuff, but i suppose the mouse should be usefull even for gpm or other non-X stuff, and having no mouse driver module loaded after the reboot is not a nice thing. Notice that i asked about this (altough addressed to Kamion) on irc before making the change while you where there, so you could have remarqued on it before i go forward and implemented this. If you want to discuss a design decision, this mailing list would be far better than the transient and overfilled medium of IRC. So, if this is not the right place for registering this module for future use, what is ? discover, which has trouble handling more than one module per pci id ? hotplug ? The X configuration stuff ? i have some doubt about Branden accepting this kind of stuff though, unless there is a generic module loading mechanism for X, and this doesn't solve the case of non-X mouse users. mdetect seems like clearly the right place. Its package description and its man page both suggest that gpm could easily be modified to use it (indeed, mdetect's default behaviour is to produce output suitable for configuring gpm). Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
