[Arm-netbook] SATA - ATAS

[luke.leighton]

On Tue, Sep 10, 2013 at 5:07 PM, Arokux X <arokux at gmail.com> wrote:
>
>
>
> On Tue, Sep 10, 2013 at 6:02 PM, luke.leighton <luke.leighton at gmail.com>
> wrote:
>>
>> On Tue, Sep 10, 2013 at 4:57 PM, Arokux X <arokux at gmail.com> wrote:
>>
>> > Luke, have you added something important to you branch?
>>
>>  yes.  fixed a segfault in the USB code [buffer overrun].  i _did_
>> inform people of this.
>>
>> > Otherwise instead of
>> > poking ancient stuff give sunxi-3.4 a shot.
>>
>>  ... which from what i gather doesn't have any working USB.  so anyone
>> using g_ether is f****d and can't connect to the device.
>>
>>  have the USB issues been tracked down yet?  i notice it's sunxi_usb
>> not sun7i_usb (and the sun7i_usb stuff was what had the segfault).
>> although it's a mentor graphics USB controller the width of the
>> registers are different (ok, their offsets / addresses, at least)
>
>
> Ah, so to be happy you need USB OTG support?

 really, yes.  i'm taking the board out of the MEB, putting it into
the flying squirrel (which doesn't have ethernet, and its USB hub
isn't tested yet).  the only way to maintain power *and* connectivity
is through USB-OTG g_ether.


> I'm not aware of its current
> status there is guy working on it though. USB host controllers are working
> fine though. Could you maybe point me to the e-mail where you describe the
> segfault,

 there's no segfault - it just doesn't work.  not detected, or not the
correct script.fex settings, or... i don't know.  i'm using 3.3 in the
meantime.  i _did_ notice that there are changes to script.fex naming
conventions which could be the issue, but i've not investigated as i
really need to get on with the flying squirrel testing.  summary:
tried 3.4, no USB, went back to 3.3

l.