Skip to contentSkip to conversation

omap_apollon_2420_defconfig

DISCUSSION Russell King - ARM Linux 6 participants 9 messages Feb 9, 2009 – Feb 20, 2009 3 messages not in the archive USB

lore
Share & tools
lore
#0 lore raw

It would be nice to get the last OMAP defconfig in mainline working. It's broken since 2.6.29-rc2-git3 due to this persistent problem:

drivers/built-in.o: In function `omap_udc_probe':
omap.c:(.init.text+0x30cc): undefined reference to otg_get_transceiver' omap.c:(.init.text+0x38a4): undefined reference to otg_put_transceiver'

#1 lore raw
Quoted 6 lines · Russell King - ARM Linux

It would be nice to get the last OMAP defconfig in mainline working. It's broken since 2.6.29-rc2-git3 due to this persistent problem:

drivers/built-in.o: In function `omap_udc_probe':
omap.c:(.init.text+0x30cc): undefined reference to otg_get_transceiver' omap.c:(.init.text+0x38a4): undefined reference to otg_put_transceiver'

Hmm, looks like 2bf5fa13fc8e34d7b86307b99f64a24cb7a83852 did not fix it. Dave, do you already have a patch for this?

Regards,

Tony

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

Hi,

In the previous patch, it's only fixed host side. But apollon case, it only used udc, so udc configuration should select USB_OTG_UTILS also.

---

drivers/usb/gadget/Kconfig +1 -0
index 3219d13..b26d6e6 100644
@@ -191,6 +191,7 @@ config USB_GADGET_OMAP
 	boolean "OMAP USB Device Controller"
 	depends on ARCH_OMAP
 	select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
+	select USB_OTG_UTILS if ARCH_OMAP
 	help
 	   Many Texas Instruments OMAP processors have flexible full
 	   speed USB device controllers, with support for up to 30
Quoted 11 lines · Tony Lindgren
Quoted 6 lines · Russell King - ARM Linux

It would be nice to get the last OMAP defconfig in mainline working. It's broken since 2.6.29-rc2-git3 due to this persistent problem:

drivers/built-in.o: In function `omap_udc_probe':
omap.c:(.init.text+0x30cc): undefined reference to otg_get_transceiver' omap.c:(.init.text+0x38a4): undefined reference to otg_put_transceiver'

Hmm, looks like 2bf5fa13fc8e34d7b86307b99f64a24cb7a83852 did not fix it. Dave, do you already have a patch for this?

Quoted 8 lines

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#4 lore raw
Quoted 6 lines · Kyungmin Park

Hi,

In the previous patch, it's only fixed host side. But apollon case, it only used udc, so udc configuration should select USB_OTG_UTILS also.

... Greg, this should be a 2.6.29-rc patch (buildfix).

Quoted 41 lines

---

drivers/usb/gadget/Kconfig +1 -0
index 3219d13..b26d6e6 100644
@@ -191,6 +191,7 @@ config USB_GADGET_OMAP
 	boolean "OMAP USB Device Controller"
 	depends on ARCH_OMAP
 	select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
+	select USB_OTG_UTILS if ARCH_OMAP
 	help
 	   Many Texas Instruments OMAP processors have flexible full
 	   speed USB device controllers, with support for up to 30
Quoted 11 lines · Tony Lindgren
Quoted 6 lines · Russell King - ARM Linux

It would be nice to get the last OMAP defconfig in mainline working. It's broken since 2.6.29-rc2-git3 due to this persistent problem:

drivers/built-in.o: In function `omap_udc_probe':
omap.c:(.init.text+0x30cc): undefined reference to otg_get_transceiver' omap.c:(.init.text+0x38a4): undefined reference to otg_put_transceiver'

Hmm, looks like 2bf5fa13fc8e34d7b86307b99f64a24cb7a83852 did not fix it. Dave, do you already have a patch for this?

Quoted 8 lines

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 9c9fda240902091754q7f723bf2ha46206e52641297b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

#6 lore raw
Quoted 2 lines · Kyungmin Park

In the previous patch, it's only fixed host side. But apollon case, it only used udc, so udc configuration should select USB_OTG_UTILS also.

So, it's 10 days later, mainline is still broken. In fact, this is now the only ARM defconfig which is failing.

What's happening? Is someone going to ack this patch? Is it going to be submitted to me or is it going to be submitted via some USB tree?

Sick of chasing people about build errors. People here need to get off their lazy backsides, check kautobuild regularly and submit build fixes.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Acked-by
#7 lore raw
Quoted 10 lines · Russell King - ARM Linux
Quoted 2 lines · Kyungmin Park

In the previous patch, it's only fixed host side. But apollon case, it only used udc, so udc configuration should select USB_OTG_UTILS also.

So, it's 10 days later, mainline is still broken. In fact, this is now the only ARM defconfig which is failing.

What's happening? Is someone going to ack this patch? Is it going to be submitted to me or is it going to be submitted via some USB tree?

Well it would be nice to get an ack from the USB people, here's mine:

Quoted 3 lines

Sick of chasing people about build errors. People here need to get off their lazy backsides, check kautobuild regularly and submit build fixes.

How about automatic notifications on the failing omap builds sent to to linux-omap list? The 34xx builds failing because of the compiler should be filtered out until the compiler is updated though.

Tony

A message that is not in the archive (sent off-list or not yet received): [email protected]

#9 lore raw
Quoted 7 lines · Tony Lindgren
Quoted 6 lines · Russell King - ARM Linux
Quoted 2 lines · Kyungmin Park

In the previous patch, it's only fixed host side. But apollon case, it only used udc, so udc configuration should select USB_OTG_UTILS also.

So, it's 10 days later, mainline is still broken. In fact, this is now the only ARM defconfig which is failing.

Really, it's actually almost one month later. I checked. I brought this issue up 27th January and then again on 9th February and here we are *three* *and* *a* *half* *weeks* later no further forward.

This is plain and simple not acceptable.

Quoted 7 lines
Quoted 3 lines

What's happening? Is someone going to ack this patch? Is it going to be submitted to me or is it going to be submitted via some USB tree?

Well it would be nice to get an ack from the USB people, here's mine:

Right, so one ack which is progress. That still leaves the question about how the patch gets into mainline.

Quoted 7 lines
Quoted 3 lines

Sick of chasing people about build errors. People here need to get off their lazy backsides, check kautobuild regularly and submit build fixes.

How about automatic notifications on the failing omap builds sent to to linux-omap list? The 34xx builds failing because of the compiler should be filtered out until the compiler is updated though.

Well, 17 days ago, the compiler was upgraded and the OMAP34xx builds started to complete. So your statement tells me that you've not looked at kautobuild for at least the last 17 days.

If you want any features, please talk to the kautobuild people. I've nothing to do with kautobuild other than seemingly being the *sole* person who checks the kautobuild website and chases people when things get broken.

Having done some research by reading through the kautobuild site, if you want to be mailed the results, kautobuild has its own mailing list. See
http://armlinux.simtec.co.uk/kautobuild/
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#10 lore raw
Quoted 30 lines · Russell King - ARM Linux
Quoted 7 lines · Tony Lindgren
Quoted 6 lines · Russell King - ARM Linux
Quoted 2 lines · Kyungmin Park

In the previous patch, it's only fixed host side. But apollon case, it only used udc, so udc configuration should select USB_OTG_UTILS also.

So, it's 10 days later, mainline is still broken. In fact, this is now the only ARM defconfig which is failing.

Really, it's actually almost one month later. I checked. I brought this issue up 27th January and then again on 9th February and here we are *three* *and* *a* *half* *weeks* later no further forward.

This is plain and simple not acceptable.

Quoted 7 lines
Quoted 3 lines

What's happening? Is someone going to ack this patch? Is it going to be submitted to me or is it going to be submitted via some USB tree?

Well it would be nice to get an ack from the USB people, here's mine:

Right, so one ack which is progress. That still leaves the question about how the patch gets into mainline.

Quoted 4 lines
Quoted 3 lines

Sick of chasing people about build errors. People here need to get off their lazy backsides, check kautobuild regularly and submit build fixes.

Quoted 7 lines
Quoted 3 lines

How about automatic notifications on the failing omap builds sent to to linux-omap list? The 34xx builds failing because of the compiler should be filtered out until the compiler is updated though.

Well, 17 days ago, the compiler was upgraded and the OMAP34xx builds started to complete. So your statement tells me that you've not looked at kautobuild for at least the last 17 days.

Great, I wonder what other fabulous websites I've forgotten!

Quoted 8 lines

If you want any features, please talk to the kautobuild people. I've nothing to do with kautobuild other than seemingly being the *sole* person who checks the kautobuild website and chases people when things get broken.

Having done some research by reading through the kautobuild site, if you want to be mailed the results, kautobuild has its own mailing list. See
http://armlinux.simtec.co.uk/kautobuild/

OK, I'll take a look at getting some automated warnings from there to linux-omap list at some point when I get around to it.

Tony

#11 lore raw
In reply to a message not in the archive
Quoted 8 lines · Tony Lindgren
Quoted 7 lines · Russell King - ARM Linux
Quoted 2 lines · Kyungmin Park

In the previous patch, it's only fixed host side. But apollon case, it only used udc, so udc configuration should select USB_OTG_UTILS also.

So, it's 10 days later, mainline is still broken. In fact, this is now the only ARM defconfig which is failing.

Quoted 7 lines
Quoted 3 lines

What's happening? Is someone going to ack this patch? Is it going to be submitted to me or is it going to be submitted via some USB tree?

Well it would be nice to get an ack from the USB people, here's mine:

I thought this was already handled ... evidently not, so I just sent it to Greg as a buildfix.

Quoted 3 lines
Quoted 3 lines

Sick of chasing people about build errors. People here need to get off their lazy backsides, check kautobuild regularly and submit build fixes.

Actually the *standard* practice involves

(a) bugs getting reported
(b) patches getting provided
(c) nagging until the patches merge

I can't fault anyone for sticking to that process and not going out of their way to seek out kautobuild issues; there's already *way* too much to do.

Quoted 3 lines

How about automatic notifications on the failing omap builds sent to to linux-omap list? The 34xx builds failing because of the compiler should be filtered out until the compiler is updated though.

That's a much better solution. I'd suggest no more than one such nag message a week though.

Quoted 4 lines

Tony

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html