linux-kernel - Re: [PATCH 2/2] Revert "ARM: RX-51: Enable isp1704 power on/off"

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 Dec 2011 12:57:50 +0200
From:	Felipe Contreras <felipe.contreras@...il.com>
To:	kalle.jokiniemi@...ia.com
Cc:	felipe.contreras@...ia.com, linux-kernel@...r.kernel.org,
	heikki.krogerus@...ia.com, cbouatmailru@...il.com, tony@...mide.com
Subject: Re: [PATCH 2/2] Revert "ARM: RX-51: Enable isp1704 power on/off"

On Wed, Dec 7, 2011 at 9:14 AM,  <kalle.jokiniemi@...ia.com> wrote:
> Reverting this patch will cause 14,7mA leak from the ISP1704 USB transceiver. I did test at the time that USB networking was ok on MeeGo 1.1 based (MeeGo community edition N900) release and this patch. Though can't help debugging this now, sorry.
>
> If you guys are not concerned with use time, no problem with this patch.

I think USB networking is more important that 14.7mA leak. So, my
setup is very simple, I build a basic user-space system with buildroot
that basically just has a shell (busybox), I configure usb0 as usual,
and it doesn't work from the PC side. Also, I never see the message
saying that the link was detected.

I tried a few things, perhaps I could try building with ISP1704
built-in, and try g_nokia instead of g_ether, but regardless of the
results, I think the patch should be reverted because it doesn't work
on some setups (mine).

-- 
Felipe Contreras
--
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/