[maemo-developers] [maemo-developers] Using the N770/N800 as a remote control.

[From: Jon Smirl]

On 1/10/07, klaus at rotters.de <klaus at rotters.de> wrote:
> Am 9 Jan 2007 um 21:52 hat Jon Smirl geschrieben:
> > Is it no power at all, or just not very much power? With no power you
>
> No power. Rumors said, that it is because there is nowehere inside the N770 +5 Volt, the
> device runs with 3.3 V or less. Since I don't have the schematics, I can't prove that.

So how about the N800, does it have power? Is it a complete USB OTG
implementation?

770 puts out a USB OTG descriptor when it isn't compliant.

On 1/10/07, David Brownell <david-b at pacbell.net> wrote:
> On Tuesday 09 January 2007 10:26 pm, Jon Smirl wrote:
> > On 1/9/07, David Brownell <david-b at pacbell.net> wrote:
> > > >               It has a high speed USB
> > > > OTG port (host/client)
> > >
> > > That's the N800 ... uses a TUSB6010 chip, the driver for which was a PITA
> > > but it basically works.  (And the CPU is much faster than the N770; it
> > > uses an ARMv6 CPU, running at a faster clock rate.)
> > >
> > > As I understand, the device has a Mini-B port, not a Mini-AB.  But other
> > > than that it's pretty much ready to be a dual-role device ... not full
> > > fledged OTG yet, but I've certainly observed the cable based role switch
> > > stuff to work.
> >
> > 770 is supposed to have OTG too.
>
> Not without providing at least 8ma VBUS power and a Mini-AB connector
> it isn't.  Instead, it provides 0mA VBUS power and a Mini-B connector.  :)
>
> The Tahvo chip has a USB transceiver that's not really OTG-capable.
> But it can do "dual role", that is it can switch between host and
> peripheral modes ... which is an OTG thing, if done the OTG way.
> Which means initial role sensing via the cable connected to the Mini-AB
> port, and HNP support to automatically switch roles later.
>
>
> > I got the network to work. Seems there are problems with having the
> > net and storage running simultaneously. This has an OTG Descriptor in
> > it that is new to me.
>
> It's a standard OTG descriptor, but the device shouldn't be putting
> one out since it's not OTG-conformant.
>
> - Dave
>

-- 
Jon Smirl
jonsmirl at gmail.com