Re: linux-image-2.6-17-mac tries

2006-09-20 Thread Brian Morris
i hate to report this, but the option to disable PDMA actually was not enough for the obsolete disk i had. says it is SCSI 1 CCS, which stands for "Common Command Set", it is supposed to provide the non optional subset of scsi 2, (according to some reference book by FWB). its pretty clear that's

Re: [buildd] buildd's running 2.2.x?

2006-09-20 Thread Michael Schmitz
> > [EMAIL PROTECTED]:~$ uname -a > > Linux q650 2.6.17-2-mac #1 Tue Aug 15 23:35:34 CEST 2006 m68k GNU/Linux > > > > Works fine; I'll restart the buildd for unstable and get back to hacking > > atafb. > > Nice. Is the keyboard working as well or is this kernel actually usable on > the majority of

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Thomas Bushnell BSG
Stephen R Marenka <[EMAIL PROTECTED]> writes: > True, but I've filed a number of such bugs only to find they were gcc > toolchain problems. Many others were ignored out right, since we're > not RC. I hadn't intended to file that bug until I had ruled out the > compiler and maybe could file an in

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Wouter Verhelst
On Tue, Sep 19, 2006 at 09:22:29PM -0400, Filipus Klutiero wrote: > Wouter Verhelst a écrit : > >Even if you still think that doing this early rather than late is > >necessary from your point of view, I would still like to search for > >alternatives, a compromise; say, that you create a stage in be

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Moritz Muehlenhoff
Stephen R Marenka wrote: >> My spare time is too limited to care about m68k. I'd suggest you prepare >> the m68k binary updates from the regular source updates available on >> s.d.o on your own. > > Could m68k still do security building out of wanna-build? Of course, you could also have continued

Re: linux-image-2.6-17-mac tries

2006-09-20 Thread Michael Schmitz
> > Welcome to my world of m68k Macs. The ESP driver has no PDMA either, > > right? > > I'm pretty sure that PDMA never worked on mac_esp, but it also wasn't > as slow without it. The 5380 chip is pretty slow even compared to the Well, it's definitely a lot slower than the 5380 with DMA. > 53c94

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Steve Langasek
On Tue, Sep 19, 2006 at 08:12:13AM -0500, Stephen R Marenka wrote: > Roman Zippel has done some serious and great work fixing our toolchain > over the past two months or so. We're down to about 16 packages blocking > 146 or so and a total of 72 packages failed due to m68k-specific problems. > Th

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Steve Langasek
On Tue, Sep 19, 2006 at 04:42:16AM -0700, Brian Morris wrote: > competitiveness as a philosophy of more or mightier > is better is to me also inconsistent with the values of > free software. The reason m68k has been disqualified as a release architecture has nothing to do with competition with oth

Re: [buildd] buildd's running 2.2.x?

2006-09-20 Thread Ingo Juergensmann
On Fri, Sep 15, 2006 at 02:22:13PM -0500, Stephen R Marenka wrote: > ij: might be nice if your buildd.net agent could list the current > running kernel too? v0.95 of update-buildd.net has support for kernel version reporting: http://buildd.net/cgi/hostpackages.cgi?unstable_arch=m68k&searchtype=sp

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Stephen R Marenka
On Tue, Sep 19, 2006 at 11:09:53PM +0200, Moritz Muehlenhoff wrote: > Wouter Verhelst wrote: > > August 16 birthday party in Breda, I discussed this with Jeroen Van > > Wolffelaar who told me that in theory, it should not be very hard to > > create a suite in dak to allow us to have a mostly-etch d

Re: [buildd] buildd's running 2.2.x?

2006-09-20 Thread Stephen R Marenka
On Wed, Sep 20, 2006 at 05:27:22PM +0200, Michael Schmitz wrote: > > > > Works fine; I'll restart the buildd for unstable and get back to hacking > > > > atafb. > > > > > > Nice. Is the keyboard working as well or is this kernel actually usable on > > > the majority of our macs? > > > > I just trie

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Moritz Muehlenhoff
Wouter Verhelst wrote: > August 16 birthday party in Breda, I discussed this with Jeroen Van > Wolffelaar who told me that in theory, it should not be very hard to > create a suite in dak to allow us to have a mostly-etch distribution; > one that is only slightly different from the 'real' etch. Giv

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Stephen R Marenka
On Wed, Sep 20, 2006 at 12:02:07AM -0700, Steve Langasek wrote: > On Tue, Sep 19, 2006 at 08:12:13AM -0500, Stephen R Marenka wrote: > > I think we do need to have a discussion about ports that don't build the > > full archive, but otherwise can make a stable release and get security > > support

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Filipus Klutiero
Wouter Verhelst a écrit : Even if you still think that doing this early rather than late is necessary from your point of view, I would still like to search for alternatives, a compromise; say, that you create a stage in between 'not considered' and 'fully considered', where e.g. a package could

Re: m68k not a release arch for etch; status in testing, future plans?

2006-09-20 Thread Bill Allombert
On Sun, Sep 17, 2006 at 11:55:02PM -0700, Steve Langasek wrote: > Hi folks, > > It's with some regret that I have to confirm that m68k is not going to be a > release architecture for etch. Time will tell. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRI

Re: linux-image-2.6-17-mac tries

2006-09-20 Thread Geert Uytterhoeven
On Tue, 19 Sep 2006, Meelis Roos wrote: > I tried current 2.6.17-2-mac (2.6.17-9) on a Quadra 840AV. Mostly no > news - it seems to work with the same problems as before (no RTC, no > serial). Even keyboard worked fine for simple login session. > > I tried with no initrd at all, althoygh one was m