Re: [patch 1/2] m68k: Atari EtherNAT (SMC91C111) driver (updated)

On Fri, 5 Sep 2008, Michael Schmitz wrote: > > > Interrupts are still missing, the driver operates from a timer routine > > > instead. > > > > Thanks, updated. But... it doesn't seem to compile? > > > > drivers/net/atari_91C111.c: In function 'smc_rcv': > > drivers/net/atari_91C111.c:584: error:

Re: [buildd] releasing lenny

Hi, No, no binaries from lenny will be going back into unstable to make sure. If it becomes an issue, it isn't very difficult to resign the changes files after the fact. If you say so - no further objections from my part. Regarding archive administration - I suppose Stephen has access to that

Re: [buildd] releasing lenny

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 No, no binaries from lenny will be going back into unstable to make sure. If it becomes an issue, it isn't very difficult to resign the changes files after the fact. Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: http

Re: [buildd] releasing lenny

Hi Michael, It's just a pain getting everything resigned by a DD and I don't use a buildd for most of these builds so there are no build logs ATM anyway. I agree it's a pain - I was wondering whether it's worth the pain myself, that's why I asked the question. Build logs are not the issue - t

Re: [buildd] releasing lenny

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It's just a pain getting everything resigned by a DD and I don't use a buildd for most of these builds so there are no build logs ATM anyway. I still need to make changes to dports w-b, and these binaries will never be released with Debian. I am a NM,

Re: [patch 1/2] m68k: Atari EtherNAT (SMC91C111) driver (updated)

Interrupts are still missing, the driver operates from a timer routine instead. Thanks, updated. But... it doesn't seem to compile? drivers/net/atari_91C111.c: In function 'smc_rcv': drivers/net/atari_91C111.c:584: error: implicit declaration of function 'readsw' Odd - that should have been

[patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Geert, as you've probably noticed, my previous EtherNAT patch does not compile without this one being applied as well. Comments welcome (is there anyone on this list with access to an EtherNAT card, besides cts and myself?). Regarding performance afforded by having a 100 Mbit PHY instead of

Re: [buildd] moving to dports, volume 1

Hi, debian-ports does not currently handle contrib or non-free. Does anyone have strong feelings about this? If we want non-free, we'll have to check licenses since we might not be considered Debian. As for contrib, I know penguin, the traditional mac bootloader, currently resides there. Mean

Re: [buildd] releasing lenny

Hi, On Thu, 4 Sep 2008, Stephen R Marenka wrote: Michael Casadevall believes we can stage lenny on dports. However, he'll need upload rights to make that happen. Per the Kiel meeting, we established that dd's would need to control the archive and machines. Since our lenny will never be part o

Re: [patch 1/2] m68k: Atari EtherNAT (SMC91C111) driver (updated)

On Thu, 4 Sep 2008, Michael Schmitz wrote: > attached is the updated Atari EtherNAT aka SMC91C111 ethernet driver. The > driver is functional (i.e. does no longer mangle the first two bytes of a > packet). > > I had to fudge with the SMC_PUSH_DATA function (the register interface appears > to be l

[buildd] releasing lenny

Michael Casadevall believes we can stage lenny on dports. However, he'll need upload rights to make that happen. Per the Kiel meeting, we established that dd's would need to control the archive and machines. Since our lenny will never be part of debian. I don't see a risk to the archive, so long

[buildd] moving to dports, volume 1

debian-ports has a limited number of GPG keys allowed to upload packages. Should any other dd's (like to) be on this list? cts luk schmitz smarenka wouter debian-ports does not currently handle contrib or non-free. Does anyone have strong feelings about this? If we want non-free, we'll have to

[patch 2/2] m68k: Atari EtherNAT (compile warning fix)

Hi Geert, this one is mainly cosmetic - that wasn't the cause of my packet mangling, after all. Cheers, Michael --- linux-2.6-geert/drivers/net/smc91x.h +++ linux-2.6/drivers/net/smc91x.h @@ -1294,7 +1294,7 @@ DATA_REG(lp)); \ } \ } else if (SMC_16BIT(lp))\ -