On Sat, Apr 08, 2006 at 10:42:58AM -0700, Brad Boyer wrote:
> On Fri, Apr 07, 2006 at 06:50:54AM -0500, Colin Watson wrote:
> > On Fri, Mar 03, 2006 at 02:30:36PM -0800, Brad Boyer wrote:
> > > On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> > > > So, my questions would be:
> > > > - w
On Fri, Apr 07, 2006 at 06:50:54AM -0500, Colin Watson wrote:
> On Fri, Mar 03, 2006 at 02:30:36PM -0800, Brad Boyer wrote:
> > On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> > > So, my questions would be:
> > > - which driver is actually needed in the case of #345467
> >
> > swim3.k
On Fri, Mar 03, 2006 at 02:30:36PM -0800, Brad Boyer wrote:
> On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> > So, my questions would be:
> > - which driver is actually needed in the case of #345467
>
> swim3.ko
>
> > - is this driver available on the root floppy (built in or module
On Tue, Mar 07, 2006 at 06:41:47AM -0600, vinai wrote:
> I made a few small changes to the interrupt call routines so the driver
> would compile and work, but was informed that those changes were not
> SMP-clean. Then I got lost in work ...
I certainly understand. I haven't had time to do anythin
On Mon, 6 Mar 2006, Brad Boyer wrote:
On Sun, Mar 05, 2006 at 02:01:23AM +0100, Marco d'Itri wrote:
[EMAIL PROTECTED] wrote:
I guess we are using udev, but with a devfs-like naming scheme on
top, right ? I strongly believe that swim3.ko is not hotplug
friendly, or that udev has some trouble
On Sun, Mar 05, 2006 at 02:01:23AM +0100, Marco d'Itri wrote:
> [EMAIL PROTECTED] wrote:
> >I guess we are using udev, but with a devfs-like naming scheme on top, right
> >?
> >I strongly believe that swim3.ko is not hotplug friendly, or that udev has
> >some trouble with builtin modules, but i wo
On Sun, Mar 05, 2006 at 11:35:55PM +0100, Marco d'Itri wrote:
> On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
>
> > I believe it would be best for all involved if we maintained a list of such
> > cases, and had proper workaround in either udev or a separate package, and
> > then, actively sear
On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
> I believe it would be best for all involved if we maintained a list of such
> cases, and had proper workaround in either udev or a separate package, and
> then, actively search to get those cases fixed in the kernel, either by doing
> the develop
On Sun, Mar 05, 2006 at 08:39:28PM +0100, Marco d'Itri wrote:
> On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
> > So, on one hand you say you have no plan to oppose workarounds, but on the
> > other hand you clearly oppose such workarounds ?
> No, I oppose attempts to require me to maintain the
On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
> Well, i remember some issues with the firewire module in the sarge timeframe,
> and how you actively discouraged a workaround for this.
It's hard to be specific since I do not remember the details either, but
IIRC I suggested a solution to be im
On Sun, Mar 05, 2006 at 04:25:01PM +0100, Marco d'Itri wrote:
> On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
>
> > > By saying that these obsolete drivers should be supported anyway you are
> > > basically requesting other people to spend their time maintaining
> > > workarounds in their own
On Mar 05, Sven Luther <[EMAIL PROTECTED]> wrote:
> > By saying that these obsolete drivers should be supported anyway you are
> > basically requesting other people to spend their time maintaining
> > workarounds in their own packages.
> Well, we have done this for sarge in a much more extensive w
On Sun, Mar 05, 2006 at 11:19:04AM +0100, Marco d'Itri wrote:
> [EMAIL PROTECTED] wrote:
>
> >I think that this is not a position acceptable in debian right now, who aims
> >to support many less-supported-arches/subarches, who still struggle to get
> >their main patches into mainline. So i believe
On Sun, Mar 05, 2006 at 02:01:23AM +0100, Marco d'Itri wrote:
> [EMAIL PROTECTED] wrote:
>
> >I guess we are using udev, but with a devfs-like naming scheme on top, right
> >?
> >I strongly believe that swim3.ko is not hotplug friendly, or that udev has
> >some trouble with builtin modules, but i
On Mar 05 2006, Marco d'Itri wrote:
> [EMAIL PROTECTED] wrote:
> >I guess we are using udev, but with a devfs-like naming scheme on
> >top, right ? I strongly believe that swim3.ko is not hotplug
> >friendly, or that udev has some trouble with builtin modules, but i
> >would go for the first case.
On Fri, Mar 03, 2006 at 02:30:36PM -0800, Brad Boyer wrote:
> On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> > So, my questions would be:
> > - which driver is actually needed in the case of #345467
>
> swim3.ko
>
> > - is this driver available on the root floppy (built in or module
On Fri, Mar 03, 2006 at 11:50:38PM +0100, Frans Pop wrote:
> On Friday 03 March 2006 23:30, Brad Boyer wrote:
> > Are we still using devfs, or have we moved on to using udev?
>
> The installer uses udev for current 2.6 kernels.
Then the likely explanation is that udev doesn't like devices
that ar
On Friday 03 March 2006 23:30, Brad Boyer wrote:
> Are we still using devfs, or have we moved on to using udev?
The installer uses udev for current 2.6 kernels.
pgpcgUt6C1aSt.pgp
Description: PGP signature
On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> So, my questions would be:
> - which driver is actually needed in the case of #345467
swim3.ko
> - is this driver available on the root floppy (built in or module)
> - if it's modular, is it being loaded
No idea. Haven't looked. Based
On Fri, Mar 03, 2006 at 10:04:41PM +0100, Frans Pop wrote:
> On Sunday 26 February 2006 17:00, Brad Boyer wrote:
> > This problem seems pretty simple. The driver floppy.ko is for normal PC
> > style floppy controllers. Apple never did use such a beast in a Mac.
> > The swim3 driver should handle th
On Sunday 26 February 2006 17:00, Brad Boyer wrote:
> This problem seems pretty simple. The driver floppy.ko is for normal PC
> style floppy controllers. Apple never did use such a beast in a Mac.
> The swim3 driver should handle the floppy drives for all PCI Macs that
> have internal floppy drives
Sven Luther wrote:
On Sun, Feb 26, 2006 at 08:00:34AM -0800, Brad Boyer wrote:
On Sun, Feb 26, 2006 at 02:55:10PM +0100, Sven Luther wrote:
On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
I've been trying to coax the floppy images from
http://people.debian.org/~luther/d
On Sun, Feb 26, 2006 at 08:00:34AM -0800, Brad Boyer wrote:
> On Sun, Feb 26, 2006 at 02:55:10PM +0100, Sven Luther wrote:
> > On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
> > > I've been trying to coax the floppy images from
> > > http://people.debian.org/~luther/d-i/images/d
Brad Boyer wrote:
On Sun, Feb 26, 2006 at 02:55:10PM +0100, Sven Luther wrote:
On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
I've been trying to coax the floppy images from
http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy/
(where daily = 25/2/2006) to boot
On Sun, Feb 26, 2006 at 02:55:10PM +0100, Sven Luther wrote:
> On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
> > I've been trying to coax the floppy images from
> > http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy/
> > (where daily = 25/2/2006) to boot on a 7200
On Sun, Feb 26, 2006 at 10:00:23PM +0800, Tomasz Grzegurzko wrote:
> Just a quick update Sven; I got the bugger working. It looks like your root
> disk
> is missing a *whole* bunch of stuff from /dev such as /dev/floppy/0 etc and
> after a few mknod commands, I was in business. That at least got m
On Sat, Feb 25, 2006 at 11:38:55PM +0800, Tomasz Grzegurzko wrote:
> Hi Sven,
>
> I've been trying to coax the floppy images from
> http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy/
> (where daily = 25/2/2006) to boot on a 7200/75 I've picked up. The
> system boots of the disks fi
27 matches
Mail list logo
