From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "Mukund JB`." <mukundjb@esntechnologies.co.in>
Cc: hirofumi@mail.parknet.co.jp,
linux-kernel-Mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: The Linux FAT issue on SD Cards.. maintainer support please
Date: Fri, 19 Aug 2005 08:59:52 -0400 [thread overview]
Message-ID: <20050819125952.GZ6714@csclub.uwaterloo.ca> (raw)
In-Reply-To: <3AEC1E10243A314391FE9C01CD65429B391B@mail.esn.co.in>
On Fri, Aug 19, 2005 at 05:09:06PM +0530, Mukund JB`. wrote:
> To handle it in a similarly in Linux we need to support this driver with
> partitions. There looks a loop hole in the driver.
> I will verify and fix it today.
I suggest having a look at how other drivers use the add_disk call,
since it calls the partition checking code already in the kernel
automatically as far as I can tell. You really shouldn't have to write
any of the partition parsing code at all. You should just have to setup
a structure describing the disk and which major/minor numbers it uses,
and passing that to add_disk and it should deal with the rest.
> Just out of inquisitive ness.
>
> What r u the minor numbers of those zip devices.
> ll /dev/zip
> ll /dev/zip4
They are symlinks:
/dev/zip -> /dev/sda
/dev/zip4 -> /dev/sda4
sda uses major,minor: 8,0
sda1: 8.1
sda2: 8,2
...
sda15: 8,15
sdb: 8,16
sdb1: 8.17
...
sdb15: 8,31
That is how scsi does it.
If your driver supports multiple slots at once, decide how many to
support, or decide to only allow a few partitions, and space them by 8
or 16 (allowing 7 and 15 partitions respectively), and it should be easy
to deal with. sda of course accesses the whole device, while sda1 and
up are for those partitions. I am pretty sure there is standard
partition handling code in the kernel you should be accessing.
> Thanks for ur support.
> I will check with partition support in the driver & update it.
> Let me fix it there and come back.
Len Sorensen
next prev parent reply other threads:[~2005-08-19 12:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 11:39 Mukund JB`.
2005-08-19 12:59 ` Lennart Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 13:18 Mukund JB.
2005-08-24 13:28 ` Lennart Sorensen
2005-08-24 8:33 Mukund JB.
2005-08-24 13:13 ` Lennart Sorensen
2005-08-18 12:56 Mukund JB`.
2005-08-18 12:51 Mukund JB`.
2005-08-18 17:26 ` Lennart Sorensen
2005-08-17 17:02 Mukund JB`.
2005-08-17 18:50 ` Lennart Sorensen
2005-08-16 13:34 Mukund JB.
2005-08-16 13:59 ` Olivier Galibert
2005-08-16 16:09 ` Lennart Sorensen
2005-08-16 13:24 Mukund JB.
2005-08-16 16:08 ` Lennart Sorensen
2005-08-12 15:46 Mukund JB.
2005-08-12 16:00 ` Lennart Sorensen
2005-08-12 14:31 Mukund JB.
2005-08-12 14:22 Mukund JB.
2005-08-12 14:48 ` Lennart Sorensen
2005-08-11 5:27 Mukund JB.
2005-08-11 5:56 ` Marc Singer
2005-08-11 15:33 ` Lennart Sorensen
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=20050819125952.GZ6714@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mukundjb@esntechnologies.co.in \
/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
all inboxes | Powered by JetHome®