On Thu, Dec 24, 2015 at 04:42:25PM +0300, Peter Mamonov wrote:
> On Thu, 24 Dec 2015 12:48:37 +0300
> Peter Mamonov wrote:
>
> > On Wed, 23 Dec 2015 18:04:43 +0100
> > Alexander Aring wrote:
> >
> > > On Wed, Dec 23, 2015 at 07:56:44PM +0300, Peter Mamonov wrote:
> > > > On Wed, 23 Dec 2015 17:
On Thu, Dec 24, 2015 at 07:10:29PM +0300, Peter Mamonov wrote:
> Let me summarize my efforts:
>
> "Global variable" solution works fine, however it is not elegant enough:
>
> diff --git a/drivers/usb/host/ehci-hcd.c b/drivers/usb/host/ehci-hcd.c
> index 862444b..d06e001 100644
> --- a/drivers/usb
Let me summarize my efforts:
"Global variable" solution works fine, however it is not elegant enough:
diff --git a/drivers/usb/host/ehci-hcd.c b/drivers/usb/host/ehci-hcd.c
index 862444b..d06e001 100644
--- a/drivers/usb/host/ehci-hcd.c
+++ b/drivers/usb/host/ehci-hcd.c
@@ -138,0 +139,2 @@ static
On Thu, Dec 24, 2015 at 01:46:53PM +0300, Peter Mamonov wrote:
> On Wed, 23 Dec 2015 20:46:02 +0100
> Sascha Hauer wrote:
>
> > Hi Peter,
> >
> > On Wed, Dec 23, 2015 at 07:10:58PM +0300, Peter Mamonov wrote:
> > > Dear All,
> > >
> > > I've ported an UHCI driver from the u-boot to the barebox
On Thu, 24 Dec 2015 12:48:37 +0300
Peter Mamonov wrote:
> On Wed, 23 Dec 2015 18:04:43 +0100
> Alexander Aring wrote:
>
> > On Wed, Dec 23, 2015 at 07:56:44PM +0300, Peter Mamonov wrote:
> > > On Wed, 23 Dec 2015 17:35:51 +0100
> > > Alexander Aring wrote:
> > >
> > > > On Wed, Dec 23, 2015 a
On Wed, 23 Dec 2015 20:46:02 +0100
Sascha Hauer wrote:
> Hi Peter,
>
> On Wed, Dec 23, 2015 at 07:10:58PM +0300, Peter Mamonov wrote:
> > Dear All,
> >
> > I've ported an UHCI driver from the u-boot to the barebox (WIP). To
> > interoperate with the EHCI driver, the UHCI driver should be probed
On Wed, 23 Dec 2015 18:04:43 +0100
Alexander Aring wrote:
> On Wed, Dec 23, 2015 at 07:56:44PM +0300, Peter Mamonov wrote:
> > On Wed, 23 Dec 2015 17:35:51 +0100
> > Alexander Aring wrote:
> >
> > > On Wed, Dec 23, 2015 at 07:10:58PM +0300, Peter Mamonov wrote:
> > > > Dear All,
> > > >
> > >
Hi Peter,
On Wed, Dec 23, 2015 at 07:10:58PM +0300, Peter Mamonov wrote:
> Dear All,
>
> I've ported an UHCI driver from the u-boot to the barebox (WIP). To
> interoperate with the EHCI driver, the UHCI driver should be probed
> ater the EHCI driver. Both drivers are binded via the device tree
>
On Wed, Dec 23, 2015 at 07:56:44PM +0300, Peter Mamonov wrote:
> On Wed, 23 Dec 2015 17:35:51 +0100
> Alexander Aring wrote:
>
> > On Wed, Dec 23, 2015 at 07:10:58PM +0300, Peter Mamonov wrote:
> > > Dear All,
> > >
> > > I've ported an UHCI driver from the u-boot to the barebox (WIP). To
> > >
On Wed, 23 Dec 2015 17:35:51 +0100
Alexander Aring wrote:
> On Wed, Dec 23, 2015 at 07:10:58PM +0300, Peter Mamonov wrote:
> > Dear All,
> >
> > I've ported an UHCI driver from the u-boot to the barebox (WIP). To
> > interoperate with the EHCI driver, the UHCI driver should be probed
> > ater th
On Wed, Dec 23, 2015 at 07:10:58PM +0300, Peter Mamonov wrote:
> Dear All,
>
> I've ported an UHCI driver from the u-boot to the barebox (WIP). To
> interoperate with the EHCI driver, the UHCI driver should be probed
> ater the EHCI driver. Both drivers are binded via the device tree
> mechanism.
Dear All,
I've ported an UHCI driver from the u-boot to the barebox (WIP). To
interoperate with the EHCI driver, the UHCI driver should be probed
ater the EHCI driver. Both drivers are binded via the device tree
mechanism. How can i achieve the correct probe order?
Regards,
Peter
___
12 matches
Mail list logo