Re: mmc-modules should be loaded by default on ARM Kirkwood
* Frans Pop elen...@planet.nl [2009-05-25 23:05]: I disagree. The function of hw-detect, and in this case more particular disk-detect, is to ensure any hardware needed for partitioning gets made available. IMO this fits that definition perfectly. How about I simply include the udeb in the netboot initrd for that particular subarch? Against that is that it's not needed at that stage, so it's initrd bloat. And that _is_ an issue on arm. I ran into some problems while adding the functionality to hw-detect and I cannot look into it in the near future. In the meantime, I'll therefore add MMC modules to the initrd on Kirkwood. The argument about initrd bloat doesn't apply to this sub-arch since all currently supported machines have 512 MB of RAM. However, I note your and Otavio's opinion and will look into a different solution later. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
* Otavio Salvador ota...@ossystems.com.br [2009-05-25 17:20]: I'd say that you could make a module depends on it; so it will be uploaded from network or from the media (as done for other modules already). Well, I don't really see which other module should depend on it. What did you have in mind exactly? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
On Monday 25 May 2009, Martin Michlmayr wrote: The mmc-modules udeb should be downloaded automatically because installations to an SD card will be quite popular on one device. This is not done at the moment because the module is priority extra. I assume the correct way to proceed is to change the priority of this udeb to standard in linux-kernel-di-armel-2.6/package-list and ask the FTP masters to change the override file. Do they accept different priority for the same udeb for different arches? Even if they do, I doubt we really want that (too hard to keep track of such subtle differences). IMO the better solution is to load it using anna-install, either during hw-detect or early in partman, based on a (sub)architecture test. hw-detect is probably the most logical choice. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
Hello Martin, On Mon, May 25, 2009 at 5:09 PM, Martin Michlmayr t...@cyrius.com wrote: The mmc-modules udeb should be downloaded automatically because installations to an SD card will be quite popular on one device. This is not done at the moment because the module is priority extra. I assume the correct way to proceed is to change the priority of this udeb to standard in linux-kernel-di-armel-2.6/package-list and ask the FTP masters to change the override file. Is this correct? I'd say that you could make a module depends on it; so it will be uploaded from network or from the media (as done for other modules already). -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
* Frans Pop elen...@planet.nl [2009-05-25 22:30]: Do they accept different priority for the same udeb for different arches? The udeb name contains the name of the subarch, so it would be unique. IMO the better solution is to load it using anna-install, either during hw-detect or early in partman, based on a (sub)architecture test. hw-detect is probably the most logical choice. Hmm, that seems overengineered too. How about I simply include the udeb in the netboot initrd for that particular subarch? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
Hello, On Mon, May 25, 2009 at 5:38 PM, Martin Michlmayr t...@cyrius.com wrote: * Frans Pop elen...@planet.nl [2009-05-25 22:30]: Do they accept different priority for the same udeb for different arches? The udeb name contains the name of the subarch, so it would be unique. IMO the better solution is to load it using anna-install, either during hw-detect or early in partman, based on a (sub)architecture test. hw-detect is probably the most logical choice. Hmm, that seems overengineered too. How about I simply include the udeb in the netboot initrd for that particular subarch? This works but I'd prefer to not bloat the initrd with non-required modules. I'd more for hw-detect or partman as suggested by Frans. Between both I think that hw-detect is the most logical place for it. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: mmc-modules should be loaded by default on ARM Kirkwood
On Monday 25 May 2009, Martin Michlmayr wrote: * Frans Pop elen...@planet.nl [2009-05-25 22:30]: Do they accept different priority for the same udeb for different arches? The udeb name contains the name of the subarch, so it would be unique. Right. I still don't like it much. IMO the better solution is to load it using anna-install, either during hw-detect or early in partman, based on a (sub)architecture test. hw-detect is probably the most logical choice. Hmm, that seems overengineered too. I disagree. The function of hw-detect, and in this case more particular disk-detect, is to ensure any hardware needed for partitioning gets made available. IMO this fits that definition perfectly. How about I simply include the udeb in the netboot initrd for that particular subarch? Against that is that it's not needed at that stage, so it's initrd bloat. And that _is_ an issue on arm. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
