lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8d6b79304e78ba664d0500b653d25db3@agner.ch>
Date:	Sat, 26 Jul 2014 14:24:10 +0200
From:	Stefan Agner <stefan@...er.ch>
To:	Peter Chen <peter.chen@...escale.com>
Cc:	s.hauer@...gutronix.de, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, shawn.guo@...escale.com,
	b35083@...escale.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/6] vf610: Add USB support

Am 2014-07-22 02:13, schrieb Peter Chen:
> On Fri, Jul 18, 2014 at 07:01:36PM +0200, Stefan Agner wrote:
>> This patchset adds USB support for Vybrid VF610 SoC. It extends the
>> clock framework to support the USB PHY cocks, extends the device
>> tree files and adds support for the non-core registers in the
>> usbmisc_imx driver.
>>
>> This patchset needs the eSDHC length fix available in Shawn's
>> for-next branch.
>>
> 
> Why it is related to USB patchset?
> 

The eSDHC registers are just in front of the USB registers. Due to the
wrong length, the two register areas overlapped, hence the second driver
(and I think it was USB which was loaded second) could not probe
successfully.

>> The whole patchset proved to be working on a Colibri VF61. The
>> first USB controller runs in peripheral mode. I could successfully
>> use RNDIS, however with some stability issues: Suddenly the other
>> side was not reachable anymore and the interface needed to brought
>> down and back up again. I'm still investigating this.
> 
> Do you use ubuntu as host distribution? I find ubuntu will lost the
> first connection for usb-ethernet-gadget(usb0) as network interface,
> but once you re-config usb0 again (ifconfig usb0 ip up), it should work
> and will not lose connection any more.
> 

I use a Angstrom build, an OpenEmbedded distribution. I restarted the
link using ip link set dev usb0 up/down, this brought the link back in a
pingable state, however even afterwards after some seconds of iperf, the
link hanged again...

--
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ