Re: [PATCH 00/11] Atari Ethernet/USB patch series - for upstream and debian-kernel

[Michael Schmitz <schmitzmic@gmail.com>]

Christian,

thanks for this - I'm sure it will come handy for building test kernel 
packages.

Generic questions first - what is the best strategy to make Zorro boards 
work with platform device utilizing drivers?
Should I go and add code to amiga/platform.c to enumerate all Zorro 
devices and add platform devices for those,
or revert to looking up Zorro device data in the SCSI driver probe 
function? Geert?

I've seen the following output on elgar:

schmitz@elgar:~$ cat /proc/bus/zorro/devices
00    21400c00    00e90000    00010000    d1
01    0877c900    00ea0000    00010000    c1

The 21400c00 is product code I presume - what's the d1?  Which of the 
two is the SCSI board?


>>> I managed to build an amiga kernel from linux-source-3.8 (in experimental)
>>> with this command:
>>>
>>> make KBUILD_DEBARCH=m68k ARCH=m68k CROSS_COMPILE=m68k-linux-gnu- deb-pkg
>> You can just run dpkg-buildpackage -am68k???
> Because linux-source, just like linux-m68k git, does not contain a debian
> directory. The linux source package (note the missing dash) does contain a
> debian directory, but that fails because gencontrol.py does not run on my
> box (OSError: missing file or directory with no hint what file is missing).
While you can catch errors of that sort in python, it's still left to 
the programmer to provide a meaningful error message.
Shame on python's subprocess.py for not printing the missing path on 
failed exec.

File "debian/bin/gencontrol.py", line 132, in do_arch_packages
     env=kw_env)


seems to be where subprocess.py is invoked - I'd add a trace print there.

>> IMHO we should try to get to as close to the normal Debian processes
>> as possible though. I???d wager a guess and say that, if you ask, for
>> example, waldi or bwh in IRC, they???d be happy to help (as opposed to
>> see you doing some n??n-standard stuff).
> The kernels I am building are not for official use, only for testing of new
> patches. In the long run I want to understand how the offical Debian images
> are built again, but unfortunately my vacation comes to an end and the new
> semester is starting... it will be at least a month before I will have time
> to study the Debian processes again. I may try to get crest running again
> with the IDE disk before that.
If you do - what SCSI board does crest use? Can you test kernels or 
possibly just modules there for me?

Cheers,

     Michael