Re: how to introduce uevent/Udev in the driver.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Greg,

On Fri, Nov 30, 2012 at 9:59 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> On Fri, Nov 30, 2012 at 07:02:14PM +0530, chetan cr123 wrote:
>> On Thu, Nov 29, 2012 at 8:49 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>> > On Thu, Nov 29, 2012 at 06:00:17PM +0530, chetan cr123 wrote:
>> >> Hi,
>> >>
>> >> I am working on Android 4.0, Kernel Version 3.0.8
>> >> I am working on USB mass storage driver.
>> >
>> > What is wrong with the existing USB mass storage driver we have in the
>> > kernel already?  Why do you need to write a new one?
>> >
>> I am not using the existing driver. I am using cypress USB 3.0 mass
>> storage driver.
>
> Which one is that?  Do you have a pointer to it somewhere?
>
>> And another issue i am facing is i ami  loading my usb 3.0
>> driver(present in /drivers/staging/westbridge/ ) as module i.e *.ko.
>> when i do this i am getting the build error like
>> usb_gadget_register_driver() is already exported in vmlinix/ or
>> uimage.
>> how do i get rid of this error. Kindly help me.
>
> Ah, I'm amazed that that driver even builds (well, I guess it doesn't.)
> Please contact the author of that driver to fix that problem, I can't
> build it (don't have the proper cross-compiler tools), and can't test
> it, so you would be the best one to be able to resolve these types of
> bugs.
>  Sorry for not giving the full info. actually followed the wrong method of commenting the register function, since using usd_gadget_register_driver() was giving error. i commneted the export symbol of this register function and the contents inside the register function(what the register function was doing inside i am doing this by placing the contents present inside the register function i am calling in probe function. here my driver works but not able to pass or communicate to upper layer or UI.

>> >> I Right now i am not able to get any uevents or Udev events in my
>> >> driver when i plug or unplug the USB.
>> >
>> > Driver's don't get uevents.
>> > The kindly let me know what gets the uevents. should i add some code in my driver file to get uevents from Apps
>> >> Kindly guide me to get the uevents or introduce UDEV in my driver file
>> >> so that i get the events every time i plug or unplug the device.
>> >>
>> >> Once i get the uevents i need pass the uevents to application/UI and
>> >> pass the control to switch from block driver to usb mass storage
>> >> driver
>> >
>> > What is wrong with the existing framework that Android provides for this
>> > type of thing?  Doesn't that work properly?
>> >
>> existing android frame works is not working properly with my usb 3.0
>> mass storage driver.
>
> Then you need to fix that :)
>
> Again, do you have a pointer to the source for it?  Any reason why it
> isn't part of the main kernel.org tree yet?

Its not the part of kernel.org because its vendor specific and still
the vendors are in some development process and once t is completed
they might make it part of kernel.org.
>
> thanks,
>
> greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux