[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] [PATCH] Machine dependent module path extension



On 02/13/13 11:46, Alan Hourihane wrote:
On 02/13/13 11:27, Miro Kropáček wrote:

On Wed, Feb 13, 2013 at 12:11 PM, Jo Even Skarstein <joska@online.no <mailto:joska@online.no>> wrote:

    If that was the case then there wouldn't be a need for
    machine-specific
    subdirectories. Only CPU-specific.

I disagree. Having aranym.xfs, nfstderr.xdd, nfetch.xif etc in 040 directory would annoy me pretty much, it prolongs boot time. But you're right with the 030 case, it applies to me as well -- I've got the SCSI-Link network card in my TT and EtherNEC in my Falcon. Now I have to have them in the same dir... Despite this I think the current structure (000/030/040/060/mil/ara) is fine and it reflects reality of most setups. So even with unified kernels (030 = Falcon/TT/CT2, 040 = aranym/hades/milan/ab040, 060 = ct60/milan/hades) I'd like to have separate machine directories at least for aranym and milan, as these are really special hardware and most probably require modules not usable anywhere else.

Do you have the same disk installed in your TT/Falcon/Aranym/milan/hades ???

But I guess, there is a case for machine specific, as it's always optional. i.e. if it exists then the kernel will look there if it detects the machine it's on etc.

Optional always makes sense.

Miro - please send the latest full patch and I'll get it committed. We'll make adjustments as we move ahead with the restructuring of the build process with 1.19.

Alan.