From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/8] usb: Move DWC3 and some gadget options to Kconfig
Date: Thu, 7 Apr 2016 08:53:04 +0200 [thread overview]
Message-ID: <570603D0.6000308@xilinx.com> (raw)
In-Reply-To: <20160407084316.73035939@amdc2363>
On 7.4.2016 08:43, Lukasz Majewski wrote:
> Hi Michal,
>
>> On 6.4.2016 15:59, Lukasz Majewski wrote:
>>> Hi Semen,
>>>
>>>>
>>>> Hi All,
>>>>
>>>> This patch series move next options to Kconfigs/defconfigs:
>>>> - CONFIG_USB_DWC3*
>>>> - CONFIG_USB_GADGET_VBUS_DRAW
>>>> - CONFIG_USB_GADGET_DUALSPEED (partially, only for DWC3 platforms
>>>> for now)
>>>> - CONFIG_USB_GADGET_DOWNLOAD
>>>> - CONFIG_G_DNL_*
>>>>
>>>> All defconfig files were post-processed via "make savedefconfig"
>>>> rule to keep correct order of options in defconfigs.
>>>>
>>>> The whole series was tested using buildman tool for all arm boards.
>>>>
>>>
>>> I've reviewed your work and I don't have any objections.
>>>
>>> Now, I'm trying to setup python test environment (DFU, UMS), so I
>>> cannot thoroughly test it.
>>
>> test/py?
>
> Yes, indeed.
>
> I've some problems with stdin/stdout operation via u-boot-test-console
> script with using cu on my Odroid XU3.
>
> I do perform soft reset on my board (by sending "reset") and thereafter
> it seems like no output from u-boot console is examined by pexpect.
>
> I've asked Stephen for sharing his u-boot-test-console file, so he
> pointed me towards his github:
>
> https://github.com/swarren/uboot-test-hooks/blob/master/bin/u-boot-test-console
>
> I hope I will solve this problem today :-).
I am using kermit. I have seen cu too.
I am also running qemu but this should be done on real hw.
Thanks,
Michal
next prev parent reply other threads:[~2016-04-07 6:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 16:36 [U-Boot] [PATCH 0/8] usb: Move DWC3 and some gadget options to Kconfig Semen Protsenko
2016-04-05 16:36 ` [U-Boot] [PATCH 1/8] usb: gadget: Move CONFIG_USB_GADGET_VBUS_DRAW " Semen Protsenko
2016-04-05 17:35 ` Stephen Warren
2016-04-05 19:45 ` Marek Vasut
2016-04-07 11:31 ` Soeren Moch
2016-04-07 15:14 ` Sam Protsenko
2016-04-05 16:36 ` [U-Boot] [PATCH 2/8] usb: gadget: Add CONFIG_USB_GADGET_DUALSPEED " Semen Protsenko
2016-04-05 17:39 ` Stephen Warren
2016-04-05 16:36 ` [U-Boot] [PATCH 3/8] usb: dwc3: Move CONFIG_USB_DWC3 " Semen Protsenko
2016-04-05 16:36 ` [U-Boot] [PATCH 4/8] usb: gadget: Move CONFIG_USB_GADGET_DOWNLOAD " Semen Protsenko
2016-04-05 16:36 ` [U-Boot] [PATCH 5/8] usb: dwc3: Move CONFIG_USB_DWC3_GADGET/HOST " Semen Protsenko
2016-04-05 16:36 ` [U-Boot] [PATCH 6/8] usb: dwc3: Move CONFIG_USB_DWC3_OMAP " Semen Protsenko
2016-04-05 16:36 ` [U-Boot] [PATCH 7/8] usb: dwc3: Move CONFIG_USB_DWC3_PHY_* " Semen Protsenko
2016-04-05 16:36 ` [U-Boot] [PATCH 8/8] usb: gadget Move: CONFIG_G_DNL_* " Semen Protsenko
2016-04-05 19:44 ` [U-Boot] [PATCH 0/8] usb: Move DWC3 and some gadget options " Marek Vasut
2016-04-07 14:57 ` Sam Protsenko
2016-04-06 13:59 ` Lukasz Majewski
2016-04-06 17:11 ` Michal Simek
2016-04-07 6:43 ` Lukasz Majewski
2016-04-07 6:53 ` Michal Simek [this message]
2016-04-07 8:22 ` Lukasz Majewski
2016-04-07 10:31 ` Michal Simek
2016-04-11 11:24 ` Lukasz Majewski
2016-04-11 12:56 ` Sam Protsenko
2016-04-11 13:23 ` Lukasz Majewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570603D0.6000308@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox