Hi Gerd, Liming,
On Tue, Dec 4, 2012 at 6:15 PM, Gerd Hoffmann wrote:
> Hi,
>
>> Gerd,
>>
>> Is there any documentation out there on how to tell QEMU on command
>> line which EHCI you want your usb-storage to attach to?
>
> docs/usb2.txt has some examples, although those are pc-centric where th
Hi,
> Gerd,
>
> Is there any documentation out there on how to tell QEMU on command
> line which EHCI you want your usb-storage to attach to?
docs/usb2.txt has some examples, although those are pc-centric where the
ehci is created on the command line. The problem with zynx is that both
ehci c
On Tue, Dec 04, 2012 at 03:16:09PM +1000, Peter Crosthwaite wrote:
>Hi Liming, Gerd,
>
>On Tue, Dec 4, 2012 at 12:50 AM, walimis wrote:
>> On Mon, Dec 03, 2012 at 01:51:00PM +0100, Gerd Hoffmann wrote:
>>> Hi,
>>>
As said in another mail, I found that the root cause is that xilinx_zynq
Hi Liming, Gerd,
On Tue, Dec 4, 2012 at 12:50 AM, walimis wrote:
> On Mon, Dec 03, 2012 at 01:51:00PM +0100, Gerd Hoffmann wrote:
>> Hi,
>>
>>> As said in another mail, I found that the root cause is that xilinx_zynq has
>>> two EHCI controller. If we use usb-storage disk, the disk will be attac
On Mon, Dec 03, 2012 at 01:51:00PM +0100, Gerd Hoffmann wrote:
> Hi,
>
>> As said in another mail, I found that the root cause is that xilinx_zynq has
>> two EHCI controller. If we use usb-storage disk, the disk will be attached to
>> the second EHCI controller, which the kernel uses the first EHC
Hi,
> As said in another mail, I found that the root cause is that xilinx_zynq has
> two EHCI controller. If we use usb-storage disk, the disk will be attached to
> the second EHCI controller, which the kernel uses the first EHCI controller
> by default.
For the linux kernel it shouldn't matter
On Thu, Nov 29, 2012 at 12:05:14PM +1000, Peter Crosthwaite wrote:
>On Thu, Nov 29, 2012 at 12:00 PM, walimis wrote:
>> On Thu, Nov 29, 2012 at 11:43:18AM +1000, Peter Crosthwaite wrote:
>>>This was left as NULL on the initial merge due to debate on the mailing list
>>>on
>>>how to handle DMA con
On 11/29/12 02:43, Peter Crosthwaite wrote:
> This was left as NULL on the initial merge due to debate on the mailing list
> on
> how to handle DMA contexts for sysbus devices. Patch
> 9e11908f12f92e31ea94dc2a4c962c836cba9f2a was later merged to fix OHCI. This
> is the,
> equivalent fix for sysbu
On Thu, Nov 29, 2012 at 12:00 PM, walimis wrote:
> On Thu, Nov 29, 2012 at 11:43:18AM +1000, Peter Crosthwaite wrote:
>>This was left as NULL on the initial merge due to debate on the mailing list
>>on
>>how to handle DMA contexts for sysbus devices. Patch
>>9e11908f12f92e31ea94dc2a4c962c836cba9f
On Thu, Nov 29, 2012 at 11:43:18AM +1000, Peter Crosthwaite wrote:
>This was left as NULL on the initial merge due to debate on the mailing list on
>how to handle DMA contexts for sysbus devices. Patch
>9e11908f12f92e31ea94dc2a4c962c836cba9f2a was later merged to fix OHCI. This is
>the,
>equivalen
10 matches
Mail list logo