Hi Greg,
I am trying to make USB work dynamically on an OMAP board which has a
USB OTG controller. The board has a mini-AB receptacle.
My target is that whenever I insert a mini-B cable the gadget related
kernel modules must be loaded automatically so that my board works as
mass storage devi
Hi,
I recently came across the below #define
# define __iomem __attribute__((noderef, address_space(2)))
Browsing the internet I could find the following detail:
"iomem" means two separate things: it means that sparse should complain
if the pointer is ever dereferenced (it's a "noderef" p
not
sure which of the function defined in these files will be called first
and who calls them? )
Hope I am much more clear than the previous post.
Thanks Again,
Arjun
pradeep singh wrote:
On Sat, Apr 18, 2009 at 4:42 PM, Arjun Joshi wrote:
Hi Guys,
I was looking through the kernel
Hi Guys,
I was looking through the kernel sources for the MUSB drivers. I was
able to understand how the platform-driver got registered. I will be
using a Davinci EVM board with MUSBMHDRC as the host controller.
But I am not able to understand how the data transfer takes place.
Assuming I at
Hey Guys,
Need help here..
Can someone kindly reply to the below questions?
Thanks,
AJ
Arjun Joshi wrote:
Hi All,
While looking at the kernel source for USB I came across the following
trace:
From usb_init() we call usb_hub_init(). In usb_hub_init() a kernel
thread is created
Hi All,
While looking at the kernel source for USB I came across the following
trace:
From usb_init() we call usb_hub_init(). In usb_hub_init() a kernel
thread is created
(hub_thread). In the hub_thread function hub_events() is called.
Can any one kindly explain in detail what does hub_eve
Hi All,
I am new to this mailing list and to the linux kernel. So the question
below might seem a little simple. Ok here goes..
I read that "struct bus_type" object is registered with the driver core
when the specific subsytem is loaded in the kernel.
Now in context of USB, I want to know
