From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: Double 'block' link for floppy
Date: Sun, 22 May 2005 16:51:02 +0100 [thread overview]
Message-ID: <20050522165102.A25124@flint.arm.linux.org.uk> (raw)
In-Reply-To: <9a87484905052208336a50c658@mail.gmail.com>; from jesper.juhl@gmail.com on Sun, May 22, 2005 at 05:33:55PM +0200
On Sun, May 22, 2005 at 05:33:55PM +0200, Jesper Juhl wrote:
> On 5/21/05, Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> > I'm seeing an oddity with floppy:
> >
> > $ vdir /sys/devices/platform/floppy.0/
> > total 0
> > lrwxrwxrwx 1 root root 0 May 21 22:43 block -> ../../../block/fd1
> > lrwxrwxrwx 1 root root 0 May 21 22:43 block -> ../../../block/fd1
> > lrwxrwxrwx 1 root root 0 May 21 22:43 bus -> ../../../bus/platform
> > -rw-r--r-- 1 root root 4096 May 21 22:43 detach_state
> >
> > I suspect the first is actually supposed to be 'fd0' since:
> >
> > $ vdir /sys/block/fd*/device
> > lrwxrwxrwx 1 root root 0 May 21 22:52 /sys/block/fd0/device -> ../../devices/platform/floppy.0
> > lrwxrwxrwx 1 root root 0 May 21 22:52 /sys/block/fd1/device -> ../../devices/platform/floppy.0
> >
>
> I just took a look here, and I don't see what you see :
That'll be because your system is obviously configured for only one
floppy drive. Configure it for two and see what happens. (Naturally
the BIOS will complain if you don't actually have a second drive.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2005-05-22 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 21:54 Double 'block' link for floppy Russell King
2005-05-22 15:33 ` Jesper Juhl
2005-05-22 15:51 ` Russell King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050522165102.A25124@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox