On Tue 16-10-18 17:47:17, Mathias Nyman wrote:
> On 16.10.2018 14:38, Jan Kara wrote:
> > On Wed 03-10-18 16:46:05, Jan Kara wrote:
> > > On Wed 03-10-18 17:19:33, Mathias Nyman wrote:
> > > > On 02.10.2018 17:53, Jan Kara wrote:
> > > > > On Tue 02-10-18 17:01:54, Mathias Nyman wrote:
> > > > > >
On Fri, 19 Oct 2018, Josep M. Mirats Tur wrote:
> Hi Stern,
>
> > First question: Does you get similar failures if you plug the device
> > into a standard PC rather than the BeagleBone?
> >
>
> No, I checked with my desktop PC running Ubuntu 14.04 and it perfectly
> works (using exactly the same
Hi,
On Fri, Oct 19, 2018 at 05:35:29PM +0200, Josep M. Mirats Tur wrote:
> Hi,
>
> Thanks again for your answer.
>
> I changed to the newest Debian image available for BeagleBone boards:
> The Debian 9.5 - 4.14.71-ti-r80
> I disabled the usb "autosuspend" by issuing the command
> echo -1 | sudo
On Fri, 19 Oct 2018, Josep M. Mirats Tur wrote:
> Hi,
>
> Thanks again for your answer.
>
> I changed to the newest Debian image available for BeagleBone boards:
> The Debian 9.5 - 4.14.71-ti-r80
> I disabled the usb "autosuspend" by issuing the command
> echo -1 | sudo tee /sys/module/usbcore/
Thanks Alan,
So, what might be the cause for those transfers that have less data
than expected?
The camera works well since in my desktop PC just works with the same
code compiled at the Beagle.
Could it be a matter of the ARM processor clock frequency? Beagle
features ARM TI AM335x at 1GHz
Josep
On Fri, Oct 19, 2018 at 06:17:31PM +0200, Josep M. Mirats Tur wrote:
> Hi Bin,
>
> I was referring to the output of usbmon I attached in the previous
> message (attached again)
>
> I'm sorry but I do not know how to acces the kernel menuconfig to
> disable the MUSB CPPI DMA, how should I do that?
Bin,
I'm sorry but I cannot find that menuconfig at the Beagle...
Does this mean I need to compile and configure a new kernel from Debian sources?
On Fri, Oct 19, 2018 at 6:28 PM Bin Liu wrote:
>
> On Fri, Oct 19, 2018 at 06:17:31PM +0200, Josep M. Mirats Tur wrote:
> > Hi Bin,
> >
> > I was ref
On Fri, Oct 19, 2018 at 06:31:15PM +0200, Josep M. Mirats Tur wrote:
> Bin,
>
> I'm sorry but I cannot find that menuconfig at the Beagle...
Never mind, but add the following to your UBoot bootargs env instead to
disable dma.
musb_hdrc.use_dma=0
Regards,
-Bin.
On Fri, 19 Oct 2018, Josep M. Mirats Tur wrote:
> Thanks Alan,
>
> So, what might be the cause for those transfers that have less data
> than expected?
> The camera works well since in my desktop PC just works with the same
> code compiled at the Beagle.
> Could it be a matter of the ARM processo
Hi Bin,
I included the following line in the /boot/uEnv.txt file (attached for
your info):
cmdline=musb_hdrc.use_dma=0
Is this format correct?
I rebooted and checked again but still the same errors from dmesg:
[ 228.863997] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[ 229.0167
On Fri, Oct 19, 2018 at 07:19:17PM +0200, Josep M. Mirats Tur wrote:
> Hi Bin,
>
> I included the following line in the /boot/uEnv.txt file (attached for
> your info):
> cmdline=musb_hdrc.use_dma=0
I am not sure about the 'cmdline=' part. Anyway, after your board is
booted, use command 'cat /proc
Hi,
It seems correct, this is the output of sudo cat /proc/cmdline:
console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait musb_hdrc.use_dma=0
So no changes :(
Any other suggestion or idea?
Thanks
Josep M
On Fri, Oct 19, 2018 at 7:31 PM Bin
On Fri, Oct 19, 2018 at 07:33:47PM +0200, Josep M. Mirats Tur wrote:
> Hi,
>
> It seems correct, this is the output of sudo cat /proc/cmdline:
> console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
> root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait musb_hdrc.use_dma=0
It looks correct. So
Hi,
Yes, this would be the link:
http://shop-orbbec3d-com.3dcartstores.com/Astra-Mini_p_40.html
In the meanwhile I'll check my application with other board.
Do you think there might be a problem with the processor frequency?
I've also crossing e-mails with ORBBEC engineers, and their only
answer
On Fri, Oct 19, 2018 at 07:48:20PM +0200, Josep M. Mirats Tur wrote:
> Hi,
>
> Yes, this would be the link:
> http://shop-orbbec3d-com.3dcartstores.com/Astra-Mini_p_40.html
Okay, It is about $160, a bit more than my bugdet...
> In the meanwhile I'll check my application with other board.
>
> Do
Hi Bin,
> Do you know what is the usb throughput required in your test case? for
> example image format, resolution, frame rate? Is the usb data transfer
> bulk or isoch?
Yes, the image format is 640 x 480
The camera can run up to 30fps, although I do not need it and set up it to 5
The Usb data t
On Fri, 19 Oct 2018, Bin Liu wrote:
> On Fri, Oct 19, 2018 at 07:19:17PM +0200, Josep M. Mirats Tur wrote:
> > Hi Bin,
> >
> > I included the following line in the /boot/uEnv.txt file (attached for
> > your info):
> > cmdline=musb_hdrc.use_dma=0
>
> I am not sure about the 'cmdline=' part. Anywa
On Fri, Oct 19, 2018 at 02:26:51PM -0400, Alan Stern wrote:
> On Fri, 19 Oct 2018, Bin Liu wrote:
>
> > On Fri, Oct 19, 2018 at 07:19:17PM +0200, Josep M. Mirats Tur wrote:
> > > Hi Bin,
> > >
> > > I included the following line in the /boot/uEnv.txt file (attached for
> > > your info):
> > > cmd
Hi,
In any case, I double checked by setting only 1 line in the uEnv.txt file
the ouput for cat /proc/cmdline is
console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M
net.ifnames=0 quiet musb_hdrc.use_dma=0 usbcore.autosuspen
uref->usage_index can be indirectly controlled by userspace, hence leading
to a potential exploitation of the Spectre variant 1 vulnerability.
This field is used as an array index by the hiddev_ioctl_usage() function,
when 'cmd' is either HIDIOCGCOLLECTIONINDEX, HIDIOCGUSAGES or
HIDIOCSUSAGES.
Fo
On Wed, October 17, 2018 11:21 pm, Greg KH wrote:
> On Wed, Oct 17, 2018 at 02:44:51PM +, elrond...@protonmail.com wrote:
>> No more leds subdirectory for this wheel, someone reports me G29 leds
>> stays supported correctly.
>>
>> No more path: /sys/class/leds/logitechwheelpath, just my keyboar
On Fri, October 19, 2018 4:46 pm, Simon Wood wrote:
> Thanks for the report, and yes it does seem broken. I tried on
> 4.17.0-rc5+
> and it seems that the 'hid-logitech' module does not know the device ID of
> the G29 anymore.
Oh, how easily we forget things... there's a switch on the top wheel
Devices connected under Terminus Technology Inc. Hub (1a40:0101) may
fail to work after the system resumes from suspend:
[ 206.063325] usb 3-2.4: reset full-speed USB device number 4 using xhci_hcd
[ 206.143691] usb 3-2.4: device descriptor read/64, error -32
[ 206.351671] usb 3-2.4: device desc
On Fri, 19 Oct 2018, Kai-Heng Feng wrote:
> Devices connected under Terminus Technology Inc. Hub (1a40:0101) may
> fail to work after the system resumes from suspend:
> [ 206.063325] usb 3-2.4: reset full-speed USB device number 4 using xhci_hcd
> [ 206.143691] usb 3-2.4: device descriptor read/
The following changes since commit 0238df646e6224016a45505d2c111a24669ebe21:
Linux 4.19-rc7 (2018-10-07 17:26:02 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
tags/usb-4.19-final
for you to fetch changes up to 9ae24af3669111d418
25 matches
Mail list logo
