Hi,
> > > So it now uses a misc device which I named "megadev0" (the
> > > name that megarc
> > > expects), and has a dynamic minor (previoulsy a dynamic major
> > > was used).
> > The driver can not change device node name for backward
> compatibility.
> > I'm checking with application team inside for further
> clarification and update here.
>
> That is an invalid reason: There was no hardcoded device node
> previously
> (it was using a dynamically assigned major).
You're right.
I misunderstood the whole idea of creating device node.
Besides this, I don't have any objection.
I would accept the patch based on descriptoin in flowing link.
http://www.us.kernel.org/pub/linux/utils/kernel/hotplug/udev_vs_devfs
Any other comment would be appreciated.
Thank you,
> -----Original Message-----
> From: Thomas Horsten [mailto:[email protected]]
> Sent: Thursday, May 04, 2006 9:38 AM
> To: Ju, Seokmann
> Cc: [email protected]; Kolli, Neela;
> [email protected]
> Subject: RE: [PATCH] MegaRAID driver management char device
> moved to misc
>
> On Thu, 4 May 2006, Ju, Seokmann wrote:
>
> > Hi,
> >
> > For following reason, I cannot accept/approve this patch.
> > I'll update further as I get clear.
> >
> > Thank you,
> >
> > > So it now uses a misc device which I named "megadev0" (the
> > > name that megarc
> > > expects), and has a dynamic minor (previoulsy a dynamic major
> > > was used).
> > The driver can not change device node name for backward
> compatibility.
> > I'm checking with application team inside for further
> clarification and update here.
>
> That is an invalid reason: There was no hardcoded device node
> previously
> (it was using a dynamically assigned major).
>
> The only tool I know which uses this device is "megarc" from
> LSI Logic.
> This tool uses the char device /dev/megaraid0, which will be created
> correctly when using my patch and udev (the recommended setup
> for Linux
> 2.6 systems). I have tested this and it works.
>
> User-level applications should not rely on hardcoded device
> numbers in any
> case, but should use the correct device from /dev or search
> for the device
> they need in sysfs.
>
> Thomas
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
