* [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address
@ 2017-02-09 7:00 Uri Mashiach
2017-02-09 20:29 ` Tom Rini
0 siblings, 1 reply; 8+ messages in thread
From: Uri Mashiach @ 2017-02-09 7:00 UTC (permalink / raw)
To: u-boot
The following XHCI registers base address are set to OMAP5 values:
OMAP_XHCI_BASE, OMAP_OCP1_SCP_BASE, OMAP_OTG_WRAPPER_BASE
Captured crash for "usb start" command:
----------------------------------cut----------------------------------
=> usb start
starting USB...
USB0: data abort
pc : [<fff63d22>] lr : [<fff63b63>]
reloc pc : [<8081cd22>] lr : [<8081cb63>]
sp : fdf42d08 ip : fff9e040 fp : fdf42d50
r10: fff8a998 r9 : fdf42ef0 r8 : 00000000
r7 : fdf42d28 r6 : fdf42d2c r5 : fffa5c00 r4 : 00000000
r3 : 4a020000 r2 : 00000000 r1 : fdf42e78 r0 : fffa5c00
Flags: nzCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
resetting ...
----------------------------------cut----------------------------------
Fix by adding the CL-SOM-AM57x target to the XHCI registers base address
ifdef'ery.
A better fix should be based on a SOC family defines (currently
missing).
Signed-off-by: Uri Mashiach <uri.mashiach@compulab.co.il>
---
include/linux/usb/xhci-omap.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/usb/xhci-omap.h b/include/linux/usb/xhci-omap.h
index 9de80d7..89665a0 100644
--- a/include/linux/usb/xhci-omap.h
+++ b/include/linux/usb/xhci-omap.h
@@ -14,7 +14,7 @@
#define OMAP_XHCI_BASE 0x488d0000
#define OMAP_OCP1_SCP_BASE 0x4A081000
#define OMAP_OTG_WRAPPER_BASE 0x488c0000
-#elif defined CONFIG_TARGET_AM57XX_EVM
+#elif defined(CONFIG_TARGET_AM57XX_EVM) || defined(CONFIG_TARGET_CL_SOM_AM57X)
#define OMAP_XHCI_BASE 0x48890000
#define OMAP_OCP1_SCP_BASE 0x4A084c00
#define OMAP_OTG_WRAPPER_BASE 0x48880000
--
2.7.4
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address
2017-02-09 7:00 [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address Uri Mashiach
@ 2017-02-09 20:29 ` Tom Rini
2017-02-12 8:55 ` Uri Mashiach
0 siblings, 1 reply; 8+ messages in thread
From: Tom Rini @ 2017-02-09 20:29 UTC (permalink / raw)
To: u-boot
On Thu, Feb 09, 2017 at 09:00:26AM +0200, Uri Mashiach wrote:
> The following XHCI registers base address are set to OMAP5 values:
> OMAP_XHCI_BASE, OMAP_OCP1_SCP_BASE, OMAP_OTG_WRAPPER_BASE
>
> Captured crash for "usb start" command:
> ----------------------------------cut----------------------------------
> => usb start
> starting USB...
> USB0: data abort
> pc : [<fff63d22>] lr : [<fff63b63>]
> reloc pc : [<8081cd22>] lr : [<8081cb63>]
> sp : fdf42d08 ip : fff9e040 fp : fdf42d50
> r10: fff8a998 r9 : fdf42ef0 r8 : 00000000
> r7 : fdf42d28 r6 : fdf42d2c r5 : fffa5c00 r4 : 00000000
> r3 : 4a020000 r2 : 00000000 r1 : fdf42e78 r0 : fffa5c00
> Flags: nzCv IRQs off FIQs off Mode SVC_32
> Resetting CPU ...
>
> resetting ...
> ----------------------------------cut----------------------------------
>
> Fix by adding the CL-SOM-AM57x target to the XHCI registers base address
> ifdef'ery.
> A better fix should be based on a SOC family defines (currently
> missing).
Can you please go add the Kconfig symbols that would be the better
solution please? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170209/9c259f4a/attachment.sig>
^ permalink raw reply [flat|nested] 8+ messages in thread
* [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address
2017-02-09 20:29 ` Tom Rini
@ 2017-02-12 8:55 ` Uri Mashiach
2017-02-12 15:47 ` Tom Rini
0 siblings, 1 reply; 8+ messages in thread
From: Uri Mashiach @ 2017-02-12 8:55 UTC (permalink / raw)
To: u-boot
Hi Tom,
On 02/09/2017 10:29 PM, Tom Rini wrote:
> On Thu, Feb 09, 2017 at 09:00:26AM +0200, Uri Mashiach wrote:
>
>> The following XHCI registers base address are set to OMAP5 values:
>> OMAP_XHCI_BASE, OMAP_OCP1_SCP_BASE, OMAP_OTG_WRAPPER_BASE
>>
>> Captured crash for "usb start" command:
>> ----------------------------------cut----------------------------------
>> => usb start
>> starting USB...
>> USB0: data abort
>> pc : [<fff63d22>] lr : [<fff63b63>]
>> reloc pc : [<8081cd22>] lr : [<8081cb63>]
>> sp : fdf42d08 ip : fff9e040 fp : fdf42d50
>> r10: fff8a998 r9 : fdf42ef0 r8 : 00000000
>> r7 : fdf42d28 r6 : fdf42d2c r5 : fffa5c00 r4 : 00000000
>> r3 : 4a020000 r2 : 00000000 r1 : fdf42e78 r0 : fffa5c00
>> Flags: nzCv IRQs off FIQs off Mode SVC_32
>> Resetting CPU ...
>>
>> resetting ...
>> ----------------------------------cut----------------------------------
>>
>> Fix by adding the CL-SOM-AM57x target to the XHCI registers base address
>> ifdef'ery.
>> A better fix should be based on a SOC family defines (currently
>> missing).
>
> Can you please go add the Kconfig symbols that would be the better
> solution please? Thanks!
>
The SOC family symbol CONFIG_AM57XX was removed by the commit 3891a54:
"ARM: DRA7x/AM57xx: Get rid of CONFIG_AM57XX".
Maybe the symbol should be reintroduced just for the XHCI registers
section?
--
Thanks,
Uri
^ permalink raw reply [flat|nested] 8+ messages in thread
* [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address
2017-02-12 8:55 ` Uri Mashiach
@ 2017-02-12 15:47 ` Tom Rini
2017-02-13 11:46 ` Lokesh Vutla
0 siblings, 1 reply; 8+ messages in thread
From: Tom Rini @ 2017-02-12 15:47 UTC (permalink / raw)
To: u-boot
On Sun, Feb 12, 2017 at 10:55:27AM +0200, Uri Mashiach wrote:
> Hi Tom,
>
> On 02/09/2017 10:29 PM, Tom Rini wrote:
> >On Thu, Feb 09, 2017 at 09:00:26AM +0200, Uri Mashiach wrote:
> >
> >>The following XHCI registers base address are set to OMAP5 values:
> >>OMAP_XHCI_BASE, OMAP_OCP1_SCP_BASE, OMAP_OTG_WRAPPER_BASE
> >>
> >>Captured crash for "usb start" command:
> >>----------------------------------cut----------------------------------
> >>=> usb start
> >>starting USB...
> >>USB0: data abort
> >>pc : [<fff63d22>] lr : [<fff63b63>]
> >>reloc pc : [<8081cd22>] lr : [<8081cb63>]
> >>sp : fdf42d08 ip : fff9e040 fp : fdf42d50
> >>r10: fff8a998 r9 : fdf42ef0 r8 : 00000000
> >>r7 : fdf42d28 r6 : fdf42d2c r5 : fffa5c00 r4 : 00000000
> >>r3 : 4a020000 r2 : 00000000 r1 : fdf42e78 r0 : fffa5c00
> >>Flags: nzCv IRQs off FIQs off Mode SVC_32
> >>Resetting CPU ...
> >>
> >>resetting ...
> >>----------------------------------cut----------------------------------
> >>
> >>Fix by adding the CL-SOM-AM57x target to the XHCI registers base address
> >>ifdef'ery.
> >>A better fix should be based on a SOC family defines (currently
> >>missing).
> >
> >Can you please go add the Kconfig symbols that would be the better
> >solution please? Thanks!
>
> The SOC family symbol CONFIG_AM57XX was removed by the commit
> 3891a54: "ARM: DRA7x/AM57xx: Get rid of CONFIG_AM57XX".
> Maybe the symbol should be reintroduced just for the XHCI registers
> section?
Yes, sounds like we do have a case where DRA7xx is not the same as
AM57xx then?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170212/034e49f5/attachment.sig>
^ permalink raw reply [flat|nested] 8+ messages in thread
* [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address
2017-02-12 15:47 ` Tom Rini
@ 2017-02-13 11:46 ` Lokesh Vutla
2017-02-13 12:12 ` Uri Mashiach
0 siblings, 1 reply; 8+ messages in thread
From: Lokesh Vutla @ 2017-02-13 11:46 UTC (permalink / raw)
To: u-boot
On Sunday 12 February 2017 09:17 PM, Tom Rini wrote:
> On Sun, Feb 12, 2017 at 10:55:27AM +0200, Uri Mashiach wrote:
>> Hi Tom,
>>
>> On 02/09/2017 10:29 PM, Tom Rini wrote:
>>> On Thu, Feb 09, 2017 at 09:00:26AM +0200, Uri Mashiach wrote:
>>>
>>>> The following XHCI registers base address are set to OMAP5 values:
>>>> OMAP_XHCI_BASE, OMAP_OCP1_SCP_BASE, OMAP_OTG_WRAPPER_BASE
>>>>
>>>> Captured crash for "usb start" command:
>>>> ----------------------------------cut----------------------------------
>>>> => usb start
>>>> starting USB...
>>>> USB0: data abort
>>>> pc : [<fff63d22>] lr : [<fff63b63>]
>>>> reloc pc : [<8081cd22>] lr : [<8081cb63>]
>>>> sp : fdf42d08 ip : fff9e040 fp : fdf42d50
>>>> r10: fff8a998 r9 : fdf42ef0 r8 : 00000000
>>>> r7 : fdf42d28 r6 : fdf42d2c r5 : fffa5c00 r4 : 00000000
>>>> r3 : 4a020000 r2 : 00000000 r1 : fdf42e78 r0 : fffa5c00
>>>> Flags: nzCv IRQs off FIQs off Mode SVC_32
>>>> Resetting CPU ...
>>>>
>>>> resetting ...
>>>> ----------------------------------cut----------------------------------
>>>>
>>>> Fix by adding the CL-SOM-AM57x target to the XHCI registers base address
>>>> ifdef'ery.
>>>> A better fix should be based on a SOC family defines (currently
>>>> missing).
>>>
>>> Can you please go add the Kconfig symbols that would be the better
>>> solution please? Thanks!
>>
>> The SOC family symbol CONFIG_AM57XX was removed by the commit
>> 3891a54: "ARM: DRA7x/AM57xx: Get rid of CONFIG_AM57XX".
>> Maybe the symbol should be reintroduced just for the XHCI registers
>> section?
>
> Yes, sounds like we do have a case where DRA7xx is not the same as
> AM57xx then?
>
No that's not right. It is just DRA74x_EVM and AM57XX evm is using
different instances of XHCI. Ideally this base address should be coming
from DT. I don't think it is a good idea to introduce CONFIG_AM57XX.
Thanks and regards,
Lokesh
^ permalink raw reply [flat|nested] 8+ messages in thread
* [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address
2017-02-13 11:46 ` Lokesh Vutla
@ 2017-02-13 12:12 ` Uri Mashiach
2017-02-13 12:33 ` Lokesh Vutla
0 siblings, 1 reply; 8+ messages in thread
From: Uri Mashiach @ 2017-02-13 12:12 UTC (permalink / raw)
To: u-boot
On 02/13/2017 01:46 PM, Lokesh Vutla wrote:
>
>
> On Sunday 12 February 2017 09:17 PM, Tom Rini wrote:
>> On Sun, Feb 12, 2017 at 10:55:27AM +0200, Uri Mashiach wrote:
>>> Hi Tom,
>>>
>>> On 02/09/2017 10:29 PM, Tom Rini wrote:
>>>> On Thu, Feb 09, 2017 at 09:00:26AM +0200, Uri Mashiach wrote:
>>>>
>>>>> The following XHCI registers base address are set to OMAP5 values:
>>>>> OMAP_XHCI_BASE, OMAP_OCP1_SCP_BASE, OMAP_OTG_WRAPPER_BASE
>>>>>
>>>>> Captured crash for "usb start" command:
>>>>> ----------------------------------cut----------------------------------
>>>>> => usb start
>>>>> starting USB...
>>>>> USB0: data abort
>>>>> pc : [<fff63d22>] lr : [<fff63b63>]
>>>>> reloc pc : [<8081cd22>] lr : [<8081cb63>]
>>>>> sp : fdf42d08 ip : fff9e040 fp : fdf42d50
>>>>> r10: fff8a998 r9 : fdf42ef0 r8 : 00000000
>>>>> r7 : fdf42d28 r6 : fdf42d2c r5 : fffa5c00 r4 : 00000000
>>>>> r3 : 4a020000 r2 : 00000000 r1 : fdf42e78 r0 : fffa5c00
>>>>> Flags: nzCv IRQs off FIQs off Mode SVC_32
>>>>> Resetting CPU ...
>>>>>
>>>>> resetting ...
>>>>> ----------------------------------cut----------------------------------
>>>>>
>>>>> Fix by adding the CL-SOM-AM57x target to the XHCI registers base address
>>>>> ifdef'ery.
>>>>> A better fix should be based on a SOC family defines (currently
>>>>> missing).
>>>>
>>>> Can you please go add the Kconfig symbols that would be the better
>>>> solution please? Thanks!
>>>
>>> The SOC family symbol CONFIG_AM57XX was removed by the commit
>>> 3891a54: "ARM: DRA7x/AM57xx: Get rid of CONFIG_AM57XX".
>>> Maybe the symbol should be reintroduced just for the XHCI registers
>>> section?
>>
>> Yes, sounds like we do have a case where DRA7xx is not the same as
>> AM57xx then?
>>
>
> No that's not right. It is just DRA74x_EVM and AM57XX evm is using
> different instances of XHCI. Ideally this base address should be coming
> from DT. I don't think it is a good idea to introduce CONFIG_AM57XX.
>
> Thanks and regards,
> Lokesh
>
It seems that the address of register is SOC dependent.
In the current method all the target boards that use the relevant SOC
should be included in the ifdef'ery - redundant maintenance.
--
Regards,
Uri
^ permalink raw reply [flat|nested] 8+ messages in thread
* [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address
2017-02-13 12:12 ` Uri Mashiach
@ 2017-02-13 12:33 ` Lokesh Vutla
2017-02-14 9:08 ` Uri Mashiach
0 siblings, 1 reply; 8+ messages in thread
From: Lokesh Vutla @ 2017-02-13 12:33 UTC (permalink / raw)
To: u-boot
On Monday 13 February 2017 05:42 PM, Uri Mashiach wrote:
>
>
> On 02/13/2017 01:46 PM, Lokesh Vutla wrote:
>>
>>
>> On Sunday 12 February 2017 09:17 PM, Tom Rini wrote:
>>> On Sun, Feb 12, 2017 at 10:55:27AM +0200, Uri Mashiach wrote:
>>>> Hi Tom,
>>>>
>>>> On 02/09/2017 10:29 PM, Tom Rini wrote:
>>>>> On Thu, Feb 09, 2017 at 09:00:26AM +0200, Uri Mashiach wrote:
>>>>>
>>>>>> The following XHCI registers base address are set to OMAP5 values:
>>>>>> OMAP_XHCI_BASE, OMAP_OCP1_SCP_BASE, OMAP_OTG_WRAPPER_BASE
>>>>>>
>>>>>> Captured crash for "usb start" command:
>>>>>> ----------------------------------cut----------------------------------
>>>>>>
>>>>>> => usb start
>>>>>> starting USB...
>>>>>> USB0: data abort
>>>>>> pc : [<fff63d22>] lr : [<fff63b63>]
>>>>>> reloc pc : [<8081cd22>] lr : [<8081cb63>]
>>>>>> sp : fdf42d08 ip : fff9e040 fp : fdf42d50
>>>>>> r10: fff8a998 r9 : fdf42ef0 r8 : 00000000
>>>>>> r7 : fdf42d28 r6 : fdf42d2c r5 : fffa5c00 r4 : 00000000
>>>>>> r3 : 4a020000 r2 : 00000000 r1 : fdf42e78 r0 : fffa5c00
>>>>>> Flags: nzCv IRQs off FIQs off Mode SVC_32
>>>>>> Resetting CPU ...
>>>>>>
>>>>>> resetting ...
>>>>>> ----------------------------------cut----------------------------------
>>>>>>
>>>>>>
>>>>>> Fix by adding the CL-SOM-AM57x target to the XHCI registers base
>>>>>> address
>>>>>> ifdef'ery.
>>>>>> A better fix should be based on a SOC family defines (currently
>>>>>> missing).
>>>>>
>>>>> Can you please go add the Kconfig symbols that would be the better
>>>>> solution please? Thanks!
>>>>
>>>> The SOC family symbol CONFIG_AM57XX was removed by the commit
>>>> 3891a54: "ARM: DRA7x/AM57xx: Get rid of CONFIG_AM57XX".
>>>> Maybe the symbol should be reintroduced just for the XHCI registers
>>>> section?
>>>
>>> Yes, sounds like we do have a case where DRA7xx is not the same as
>>> AM57xx then?
>>>
>>
>> No that's not right. It is just DRA74x_EVM and AM57XX evm is using
>> different instances of XHCI. Ideally this base address should be coming
>> from DT. I don't think it is a good idea to introduce CONFIG_AM57XX.
>>
>> Thanks and regards,
>> Lokesh
>>
> It seems that the address of register is SOC dependent.
> In the current method all the target boards that use the relevant SOC
> should be included in the ifdef'ery - redundant maintenance.
Please have a look at the TRMs. DRA7xx[1], AM57xx[2]. Both has the above
two instances of XHCI. There is no difference.
[1] http://www.ti.com/lit/ug/sprui30b/sprui30b.pdf
[2] http://www.ti.com/lit/ug/spruhz6h/spruhz6h.pdf
Thanks and regards,
Lokesh
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address
2017-02-13 12:33 ` Lokesh Vutla
@ 2017-02-14 9:08 ` Uri Mashiach
0 siblings, 0 replies; 8+ messages in thread
From: Uri Mashiach @ 2017-02-14 9:08 UTC (permalink / raw)
To: u-boot
On 02/13/2017 02:33 PM, Lokesh Vutla wrote:
>
>
> On Monday 13 February 2017 05:42 PM, Uri Mashiach wrote:
>>
>>
>> On 02/13/2017 01:46 PM, Lokesh Vutla wrote:
>>>
>>>
>>> On Sunday 12 February 2017 09:17 PM, Tom Rini wrote:
>>>> On Sun, Feb 12, 2017 at 10:55:27AM +0200, Uri Mashiach wrote:
>>>>> Hi Tom,
>>>>>
>>>>> On 02/09/2017 10:29 PM, Tom Rini wrote:
>>>>>> On Thu, Feb 09, 2017 at 09:00:26AM +0200, Uri Mashiach wrote:
>>>>>>
>>>>>>> The following XHCI registers base address are set to OMAP5 values:
>>>>>>> OMAP_XHCI_BASE, OMAP_OCP1_SCP_BASE, OMAP_OTG_WRAPPER_BASE
>>>>>>>
>>>>>>> Captured crash for "usb start" command:
>>>>>>> ----------------------------------cut----------------------------------
>>>>>>>
>>>>>>> => usb start
>>>>>>> starting USB...
>>>>>>> USB0: data abort
>>>>>>> pc : [<fff63d22>] lr : [<fff63b63>]
>>>>>>> reloc pc : [<8081cd22>] lr : [<8081cb63>]
>>>>>>> sp : fdf42d08 ip : fff9e040 fp : fdf42d50
>>>>>>> r10: fff8a998 r9 : fdf42ef0 r8 : 00000000
>>>>>>> r7 : fdf42d28 r6 : fdf42d2c r5 : fffa5c00 r4 : 00000000
>>>>>>> r3 : 4a020000 r2 : 00000000 r1 : fdf42e78 r0 : fffa5c00
>>>>>>> Flags: nzCv IRQs off FIQs off Mode SVC_32
>>>>>>> Resetting CPU ...
>>>>>>>
>>>>>>> resetting ...
>>>>>>> ----------------------------------cut----------------------------------
>>>>>>>
>>>>>>>
>>>>>>> Fix by adding the CL-SOM-AM57x target to the XHCI registers base
>>>>>>> address
>>>>>>> ifdef'ery.
>>>>>>> A better fix should be based on a SOC family defines (currently
>>>>>>> missing).
>>>>>>
>>>>>> Can you please go add the Kconfig symbols that would be the better
>>>>>> solution please? Thanks!
>>>>>
>>>>> The SOC family symbol CONFIG_AM57XX was removed by the commit
>>>>> 3891a54: "ARM: DRA7x/AM57xx: Get rid of CONFIG_AM57XX".
>>>>> Maybe the symbol should be reintroduced just for the XHCI registers
>>>>> section?
>>>>
>>>> Yes, sounds like we do have a case where DRA7xx is not the same as
>>>> AM57xx then?
>>>>
>>>
>>> No that's not right. It is just DRA74x_EVM and AM57XX evm is using
>>> different instances of XHCI. Ideally this base address should be coming
>>> from DT. I don't think it is a good idea to introduce CONFIG_AM57XX.
>>>
>>> Thanks and regards,
>>> Lokesh
>>>
>> It seems that the address of register is SOC dependent.
>> In the current method all the target boards that use the relevant SOC
>> should be included in the ifdef'ery - redundant maintenance.
>
> Please have a look at the TRMs. DRA7xx[1], AM57xx[2]. Both has the above
> two instances of XHCI. There is no difference.
>
> [1] http://www.ti.com/lit/ug/sprui30b/sprui30b.pdf
> [2] http://www.ti.com/lit/ug/spruhz6h/spruhz6h.pdf
>
> Thanks and regards,
> Lokesh
>
The fact that the two SOCs share the same registers base doesn't
contradict the approach of selecting the registers based on the SOC.
I agree that the resolution should be higher. The exact SOC id
(CONFIG_AM572X, CONFIG_DRA74X, CONFIG_DRA75X...) should be determined by
the target selection - board file or Kconfig.
The ifdef'ery should include the exact SOCs id. According to the
provided TRMs, CONFIG_AM572X and CONFIG_DRA74X will be located in the
same ifdef'ery case.
--
Regards,
Uri
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-02-14 9:08 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-09 7:00 [U-Boot] [PATCH 1/6] arm: am57xx: cl-som-am57x: fix XHCI registers base address Uri Mashiach
2017-02-09 20:29 ` Tom Rini
2017-02-12 8:55 ` Uri Mashiach
2017-02-12 15:47 ` Tom Rini
2017-02-13 11:46 ` Lokesh Vutla
2017-02-13 12:12 ` Uri Mashiach
2017-02-13 12:33 ` Lokesh Vutla
2017-02-14 9:08 ` Uri Mashiach
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.