So this series is an effort to start a conversation in the community, with
the intent to free the Intel(R) Myriad(TM) ma24xx stack, as found within:
* USB Intel Neural Compute Stick (ma2450)
* USB Intel Neural Compute Stick 2 (ma2485)
What this patch series is:
* RFC for a helper driver t
W dniu 09.09.2019 o 14:45, Oliver Neukum pisze:
Am Mittwoch, den 04.09.2019, 19:10 +0200 schrieb Julian Sikorski:
Moreover, does this matter that the two Read Capacity errors only appear
after the device is disconnected?
Hi,
yes it does. However, it didn't in the first log I looked at.
Coul
Am Mittwoch, den 04.09.2019, 19:10 +0200 schrieb Julian Sikorski:
>
>
> Moreover, does this matter that the two Read Capacity errors only appear
> after the device is disconnected?
Hi,
yes it does. However, it didn't in the first log I looked at.
Could you check whether the command the failure
, Product=3,
SerialNumber=1
[ 67.947740] usb 2-4: Product: Rugged USB3-FW
[ 67.947741] usb 2-4: Manufacturer: LaCie
[ 67.947742] usb 2-4: SerialNumber: 157f928920fa
[ 67.978140] usbcore: registered new interface driver usb-storage
[ 68.007356] scsi host12: uas
[ 68.007520] usbcore
, Product=3,
> SerialNumber=1
> [ 67.947740] usb 2-4: Product: Rugged USB3-FW
> [ 67.947741] usb 2-4: Manufacturer: LaCie
> [ 67.947742] usb 2-4: SerialNumber: 157f928920fa
> [ 67.978140] usbcore: registered new interface driver usb-storage
> [ 68.007356] scsi host
.
[ 362.230833] usb 2-4: New USB device found, idVendor=059f,
idProduct=1061, bcdDevice= 0.01
[ 362.230837] usb 2-4: New USB device strings: Mfr=2, Product=3,
SerialNumber=1
[ 362.230839] usb 2-4: Product: Rugged USB3-FW
[ 362.230841] usb 2-4: Manufacturer: LaCie
[ 362.230842] usb 2-4
und, idVendor=059f,
> idProduct=1061, bcdDevice= 0.01
> [ 362.230837] usb 2-4: New USB device strings: Mfr=2, Product=3,
> SerialNumber=1
> [ 362.230839] usb 2-4: Product: Rugged USB3-FW
> [ 362.230841] usb 2-4: Manufacturer: LaCie
> [ 362.230842] usb 2-4: SerialNumber:
Gen 1 USB device number 3 using
xhci_hcd
[ 362.230833] usb 2-4: New USB device found, idVendor=059f,
idProduct=1061, bcdDevice= 0.01
[ 362.230837] usb 2-4: New USB device strings: Mfr=2, Product=3,
SerialNumber=1
[ 362.230839] usb 2-4: Product: Rugged USB3-FW
[ 362.230841] usb 2-4: Man
W dniu 23.08.2019 o 23:23, Oliver Neukum pisze:
> Am Freitag, den 23.08.2019, 16:21 +0200 schrieb Julian Sikorski:
>>
>> I did some further digging regarding whether this is a regression: the
>> quirk file on the laptop is from 15 July 2014. The machine is from ca.
>> May 2011. Looking through my e
Am Freitag, den 23.08.2019, 16:21 +0200 schrieb Julian Sikorski:
>
> I did some further digging regarding whether this is a regression: the
> quirk file on the laptop is from 15 July 2014. The machine is from ca.
> May 2011. Looking through my earlier posts to linux-usb it appears that
> the addit
W dniu 23.08.2019 o 15:43, Julian Sikorski pisze:
> W dniu 23.08.2019 o 15:39, Oliver Neukum pisze:
>> Am Freitag, den 23.08.2019, 15:31 +0200 schrieb Julian Sikorski:
>>> it appears that lacie rugged usb3-fw is not compatible with UAS.
>>> I have just connected my few
W dniu 23.08.2019 o 15:39, Oliver Neukum pisze:
> Am Freitag, den 23.08.2019, 15:31 +0200 schrieb Julian Sikorski:
>> it appears that lacie rugged usb3-fw is not compatible with UAS.
>> I have just connected my few years old Lacie Rugged USB3-FW to my new
>> desktop PC to see
Am Freitag, den 23.08.2019, 15:31 +0200 schrieb Julian Sikorski:
> it appears that lacie rugged usb3-fw is not compatible with UAS.
> I have just connected my few years old Lacie Rugged USB3-FW to my new
> desktop PC to see if the backups I have been creating on the laptop can
>
Dear list,
it appears that lacie rugged usb3-fw is not compatible with UAS.
I have just connected my few years old Lacie Rugged USB3-FW to my new
desktop PC to see if the backups I have been creating on the laptop can
actually be restored. I have then noticed that the drive does not work
in the
Sehr geehrte Damen und Herren,
ich wende mich an Sie, da ich der Meinung bin, dass sich die von Ihnen auf der
Webseite angebotenen Produkte ausgezeichnet dazu eignen, im Internet gefördert
zu werden.
Deshalb möchte ich Ihnen die Tools anbieten, die es erlauben, den Verkauf von
Ihren Produkten u
nst struct pci_device_id gpu_i2c_ids[] = {
};
MODULE_DEVICE_TABLE(pci, gpu_i2c_ids);
+static const struct property_entry ccgx_props[] = {
+ /* Use FW built for NVIDIA (nv) only */
+ PROPERTY_ENTRY_U16("ccgx,firmware-build", ('n' << 8) | 'v'),
+ {
nst struct pci_device_id gpu_i2c_ids[] = {
};
MODULE_DEVICE_TABLE(pci, gpu_i2c_ids);
+static const struct property_entry ccgx_props[] = {
+ /* Use FW built for NVIDIA (nv) only */
+ PROPERTY_ENTRY_U16("ccgx,firmware-build", ('n' << 8) | 'v'),
+ {
u.c
@@ -253,6 +253,12 @@ static const struct pci_device_id gpu_i2c_ids[] = {
};
MODULE_DEVICE_TABLE(pci, gpu_i2c_ids);
+static const struct property_entry ccgx_props[] = {
+ /* Use FW built for NVIDIA (nv) only */
+ PROPERTY_ENTRY_U16("ccgx,firmware-build
nst struct pci_device_id gpu_i2c_ids[] = {
};
MODULE_DEVICE_TABLE(pci, gpu_i2c_ids);
+static const struct property_entry ccgx_props[] = {
+ /* Use FW built for NVIDIA (nv) only */
+ PROPERTY_ENTRY_U16("ccgx,firmware-build", ('n' << 8) | 'v'),
+ {
pu_i2c_ids[] = {
};
MODULE_DEVICE_TABLE(pci, gpu_i2c_ids);
+static const struct property_entry ccgx_props[] = {
+ /* Use FW built for NVIDIA (nv) only */
+ PROPERTY_ENTRY_U16("ccgx,firmware-build", ('n' << 8) | 'v'),
+ { }
+};
+
static int gpu_pop
Hi Ajay,
This the example I promised. I prepared these on top of your
patches. The second patch ("usb: typec: ucsi: ccgx: Read the
fw build property") I want to squash into your patch adding
the firmware handing to the CCGx driver.
If you want to add modifications to these, resend
sync between user and driver thread */
+
+ u16 fw_build;
};
static int ccg_read(struct ucsi_ccg *uc, u16 rab, u8 *data, u32 len)
@@ -687,7 +689,7 @@ static bool ccg_check_vendor_version(struct ucsi_ccg *uc,
/* Check if the fw build is for supported vendors.
* Add all supp
On Fri, Feb 01, 2019 at 05:05:08PM -0800, Ajay Gupta wrote:
> From: Ajay Gupta
>
> Adding support for below commands which will be used
> during firmware flashing.
> - ENTER_FLASHING
> - RESET
> - PDPORT_ENABLE
> - JUMP_TO_BOOT
> - FLASH_ROW_RW
> - VALIDATE_FW
return 0;
}
+static bool ccg_check_vendor_version(struct ucsi_ccg *uc,
+struct version_format *app,
+struct fw_config_table *fw_cfg)
+{
+ struct device *dev = uc->dev;
+
+ /* Check if the fw build is for supporte
From: Ajay Gupta
Adding support for below commands which will be used
during firmware flashing.
- ENTER_FLASHING
- RESET
- PDPORT_ENABLE
- JUMP_TO_BOOT
- FLASH_ROW_RW
- VALIDATE_FW
I command specific mutex lock is also added to sync
between driver a
secondary_fw_min_ver = 41;
+
+enum enum_fw_mode {
+ BOOT, /* bootloader */
+ FW1,/* FW partition-1 (contains secondary fw) */
+ FW2,/* FW partition-2 (contains primary fw) */
+ FW_INVALID,
+};
+
+enum enum_flash_mode {
+ SECONDARY_BL, /* update secondary using
Adding support for below commands which will be used
during firmware flashing.
- ENTER_FLASHING
- RESET
- PDPORT_ENABLE
- JUMP_TO_BOOT
- FLASH_ROW_RW
- VALIDATE_FW
I command specific mutex lock is also added to sync
between driver and user threads.
S
0x
> > #define CCGX_RAB_INTR_REG 0x0006
> > #define DEV_INT BIT(0)
> > @@ -68,6 +71,27 @@
> > #define FW2_METADATA_ROW0x1FE
> > #define FW_CFG_TABLE_SIG_SIZE 256
> >
> > +enum enum_fw_m
Hi Greg,
> On Thu, Jan 17, 2019 at 05:12:38PM -0800, Ajay Gupta wrote:
> > This will be needed to check if latest fw is already flashed.
>
> Very odd changelog text, please make this more detailed.
Sure.
> And your email threading broke here, did your email client change?
Th
Hi Greg
-off-by: Ajay Gupta
> > ---
> > drivers/usb/typec/ucsi/ucsi_ccg.c | 139
> > ++
> > 1 file changed, 139 insertions(+)
> >
> > diff --git a/drivers/usb/typec/ucsi/ucsi_ccg.c
> > b/drivers/usb/typec/ucsi/ucsi_ccg.c
> > index 5f341934a5af..6069a9f60d1e 100644
> >
Hi Greg,
On Wednesday, January 23, 2019 2:09 AM, Greg KH wrote:
> On Wed, Jan 23, 2019 at 06:52:00AM +, Maynard CABIENTE wrote:
> > This e-mail, and any document attached hereby, may contain confidential
> > and/or privileged information. If you are not the intended recipient (or
> > have re
On Thu, Jan 17, 2019 at 05:12:38PM -0800, Ajay Gupta wrote:
> This will be needed to check if latest fw is already flashed.
>
> Signed-off-by: Ajay Gupta
> ---
> drivers/usb/typec/ucsi/ucsi_ccg.c | 139 ++
> 1 file changed, 139 insertions(+)
>
&
On Thu, Jan 17, 2019 at 05:12:38PM -0800, Ajay Gupta wrote:
> This will be needed to check if latest fw is already flashed.
>
> Signed-off-by: Ajay Gupta
> ---
> drivers/usb/typec/ucsi/ucsi_ccg.c | 139 ++
> 1 file changed, 139 insertions(+)
>
&
On Thu, Jan 17, 2019 at 05:12:38PM -0800, Ajay Gupta wrote:
> This will be needed to check if latest fw is already flashed.
Very odd changelog text, please make this more detailed.
And your email threading broke here, did your email client change?
thanks,
greg k-h
This will be needed to check if latest fw is already flashed.
Signed-off-by: Ajay Gupta
---
drivers/usb/typec/ucsi/ucsi_ccg.c | 139 ++
1 file changed, 139 insertions(+)
diff --git a/drivers/usb/typec/ucsi/ucsi_ccg.c
b/drivers/usb/typec/ucsi/ucsi_ccg.c
index
Adding support for commands which will be used for firmware
flashing.
Signed-off-by: Ajay Gupta
---
drivers/usb/typec/ucsi/ucsi_ccg.c | 216 ++
1 file changed, 216 insertions(+)
diff --git a/drivers/usb/typec/ucsi/ucsi_ccg.c
b/drivers/usb/typec/ucsi/ucsi_ccg.c
index
From: JackyChou
Add a new PID 0x7843 to the driver.
Let the new products be able to set up 3 serial ports with the driver.
Signed-off-by: JackyChou
---
drivers/usb/serial/mos7840.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/serial/mos7840.c b/d
On 04.09.2018 17:51, Frank Wunderlich wrote:
this fixes the issue:
adding the following lines to drivers/usb/host/xhci-mem.c line:1616
if (xhci->quirks & XHCI_MTK_HOST) {
in_ep_ctx->reserved[0] = out_ep_ctx->reserved[0];
in_ep_ctx->reserved[1] = out_ep_ctx->reserved[1];
}
com
"Mathias Nyman"
An: "Frank Wunderlich" , linux-usb@vger.kernel.org
Betreff: Re: Fw: Aw: Re: keyboard-problem on bpi-r2 since 4.17
On 04.09.2018 16:14, Frank Wunderlich wrote:
> Hi,
>
> i got an info that my issue was caused by this commit:
>
> https://git.kernel.org/
On 04.09.2018 16:14, Frank Wunderlich wrote:
Hi,
i got an info that my issue was caused by this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=217491487c43892318c18b6dcafe33b6353efd40
Patch is in progress...
That patch has been there since 4.13
If 4.16
ybe i can merge newer versions (go
>forward from it instead of backwards).
>
>regards frank
>
>Gesendet: Dienstag, 04. September 2018 um 07:26 Uhr
>Von: "Greg KH"
>An: "Frank Wunderlich"
>Cc: linux-usb@vger.kernel.org
>Betreff: Re: Fw: keyboard-
versions (go forward from
it instead of backwards).
regards frank
Gesendet: Dienstag, 04. September 2018 um 07:26 Uhr
Von: "Greg KH"
An: "Frank Wunderlich"
Cc: linux-usb@vger.kernel.org
Betreff: Re: Fw: keyboard-problem on bpi-r2 since 4.17
On Tue, Sep 04, 2018 at 06:
On Tue, Sep 04, 2018 at 06:39:20AM +0200, Frank Wunderlich wrote:
>
>
>
> Hi,
>
> i have problems with usb-keyboard on bananapi-r2 since 4.17. same keyboard
> works till 4.16.
> In 4.19-rc1 same issue occours. Keyboard is recognized and on keypress it is
> disconnected
> and connected again
Hi,
i have problems with usb-keyboard on bananapi-r2 since 4.17. same keyboard
works till 4.16.
In 4.19-rc1 same issue occours. Keyboard is recognized and on keypress it is
disconnected
and connected again without anything written to console.
dmesg (printk-debuglevel=8) looks like this:
On Thu, Dec 28, 2017 at 04:03:46PM -0800, Andrew Morton wrote:
>
> Is anyone able to reproduce this? The VM_BUG_ON_PAGE() in get_page()
> went bang.
Yep, it triggers for me.
Looks like MON_IOCT_RING_SIZE reallocates ring buffer without any
serialization wrt mon_bin_vma_fault(). By the time of g
Am Montag, den 19.06.2017, 18:18 + schrieb Abdulhadi Mohamed:
> Note that my device exposes configurations with a bInterfaceSubclass of
> 1(Boot Interface) as required.
Only those or those in addition to other configurations?
Which configuration is chosen?
Regards
Oli
Hello,
I have been trying to get my composite HID gadget to work in BIOS via the Boot
Protocol. However, I've noticed that the set_protocol() command to switch the
device to boot mode from report mode is not implemented in the hidg_setup
function in the HID function driver (f_hid.c). How hard
Am Dienstag, den 06.06.2017, 12:30 + schrieb Abdulhadi Mohamed:
> Hi
>
> I apologize in advance for this is my first email using this mailing list but
> I could really use some help. I have connected a composite USB device running
> the 4.0 Linux kernel to a PC running Ubuntu. One of its fu
Hi
I apologize in advance for this is my first email using this mailing list but I
could really use some help. I have connected a composite USB device running the
4.0 Linux kernel to a PC running Ubuntu. One of its functions is to act as a
HID device for mouse and keyboard to control the host
Am Dienstag, den 04.04.2017, 13:55 +0200 schrieb Bjørn Mork:
> Oliver Neukum writes:
> >
> > Am Montag, den 03.04.2017, 12:48 -0700 schrieb Stephen Hemminger:
> > >
> > > Looks like new warnings in usbnet
> > >
> > >
> > > ** CID 751368: Null pointer dereferences (FORWARD_NULL)
> > > /driver
Oliver Neukum writes:
> Am Montag, den 03.04.2017, 12:48 -0700 schrieb Stephen Hemminger:
>> Looks like new warnings in usbnet
>>
>>
>> ** CID 751368: Null pointer dereferences (FORWARD_NULL)
>> /drivers/net/usb/usbnet.c: 1925 in __usbnet_read_cmd()
>
> Hi Stephen,
>
> I am afraid I don't see
Am Montag, den 03.04.2017, 12:48 -0700 schrieb Stephen Hemminger:
> Looks like new warnings in usbnet
>
>
> ** CID 751368: Null pointer dereferences (FORWARD_NULL)
> /drivers/net/usb/usbnet.c: 1925 in __usbnet_read_cmd()
Hi Stephen,
I am afraid I don't see the problem. Yes, we are passing
a N
Looks like new warnings in usbnet
** CID 751368: Null pointer dereferences (FORWARD_NULL)
/drivers/net/usb/usbnet.c: 1925 in __usbnet_read_cmd()
*** CID 751368: Null pointer dereferences
Greg, hope you had not faced any issue (tab converted to spaces) with this
patch.
In case still facing any issue please let me know.
> There is race condition when two USB class drivers try to call
> init_usb_class at the same time and leads to crash.
> code path: probe->usb_register_dev->init_u
On Fri, 3 Mar 2017, Ajay Kaher wrote:
> > usb_class->kref is not accessible outside the file.c
> > as usb_class is _static_ inside the file.c and
> > pointer of usb_class->kref is not passed anywhere.
> >
> > Hence as you wanted, there are no references of usb_class->kref
> > other than taken by
> On Thr, 2 Mar 2017, Ajay Kaher wrote:
>> On Wed, 1 Mar 2017, Alan Stern wrote:
>>> On Wed, 1 Mar 2017, Ajay Kaher wrote:
On Mon, 22 Feb 2017, Ajay Kaher wrote:
>
>> Alan, as per my understanding I have shifted the lock from
>> release_usb_class() to destroy_usb_class() in
> On Wed, 1 Mar 2017, Alan Stern wrote:
>> On Wed, 1 Mar 2017, Ajay Kaher wrote:
>>> On Mon, 22 Feb 2017, Ajay Kaher wrote:
>>>
> Alan, as per my understanding I have shifted the lock from
> release_usb_class() to destroy_usb_class() in patch v3.
> If it is not right, please ex
On Wed, 1 Mar 2017, Ajay Kaher wrote:
> > On Mon, 22 Feb 2017, Ajay Kaher wrote:
> >
> >> On Mon, 20 Feb 2017, Ajay Kaher wrote:
> >>
> >>> Alan, as per my understanding I have shifted the lock from
> >>> release_usb_class() to destroy_usb_class() in patch v3.
> >>> If it is not right, please e
> On Mon, 22 Feb 2017, Ajay Kaher wrote:
>
>> On Mon, 20 Feb 2017, Ajay Kaher wrote:
>>
>>> Alan, as per my understanding I have shifted the lock from
>>> release_usb_class() to destroy_usb_class() in patch v3.
>>> If it is not right, please explain in detail which race condition
>>> I have mis
Bind to the interface, but do not register any ports, after having
downloaded the firmware. The device will still disconnect and
re-enumerate, but this way we avoid an error messages from being logged
as part of the process:
io_ti: probe of 1-1.3:1.0 failed with error -5
Signed-off-by: Johan Hovo
On Mon, 11 Jul 2016: Alan Stern wrote:
> On Mon, 11 Jul 2016, Huang, Huki wrote:
> > When end user inserts a usb3 device and put dut to s3.
> What does "dut" mean?
DUT : Device under test
> > Then hotplug the usb3 disk under s3.
> Do you mean that the device is unplugged and the USB disk then
Appears to be a cdc_ether driver bug. See Bugzilla for more followup info
Begin forwarded message:
Date: Fri, 20 Nov 2015 11:11:26 +
From: "bugzilla-dae...@bugzilla.kernel.org"
To: "shemmin...@linux-foundation.org"
Subject: [Bug 108201] New: Can connect with Huawei E3131-s2 (Hi-Link) 3G mo
On Mon, 23 Mar 2015, Marc Joliet wrote:
> > - If I leave the drive unplugged during boot and plug it in without manually
> > loading any modules, nothing happens. That is, the kernel does not log
> > anything about the device being attached, and neither the uas nor the
> > usb-storage modul
Ugh, I'm stupid. I sent the last two emails to linux-usb-owner by mistake
(that's what I get for blindly copy-n-pasting from Alan's email's headers). So
here's my last mail again:
Start weitergeleitete Nachricht:
Datum: Mon, 23 Mar 2015 11:13:25 +0100
Von: Marc Joliet
An: linux-usb-ow...@vger.
From: Kristian Evensen
Date: Fri, 2 Jan 2015 16:21:45 +0100
> From: Kristian Evensen
>
> Some buggy firmwares export an incorrect MAC address (00:a0:c6:00:00:00). This
> makes for example checking devices for random MAC addresses tricky, and you
> might end up with multiple network interfaces
From: Kristian Evensen
Some buggy firmwares export an incorrect MAC address (00:a0:c6:00:00:00). This
makes for example checking devices for random MAC addresses tricky, and you
might end up with multiple network interfaces with the same address.
This patch tries to fix, or at least improve, the
I'm no longer the USB 3.0 driver maintainer. Please work with Mathias
Nyman to fix this issue.
Sarah Sharp
On Fri, Oct 31, 2014 at 06:01:24PM +0300, parafin wrote:
> Hi,
>
> it was suggested to me that since you are the author of offending
> commit I should forward this email to you. Also see t
On 14-04-28 20:16:12, Greg KH wrote:
> On Mon, Apr 28, 2014 at 05:28:38PM -0700, Stephen Hemminger wrote:
> > Kernel Version: 3.0.94
>
> That is a many year old obsolete kernel, there's nothing we can do about
> that release, sorry. Please try 3.14
I've fixed a few important bugs in 3.10 so
On Mon, Apr 28, 2014 at 05:28:38PM -0700, Stephen Hemminger wrote:
> Kernel Version: 3.0.94
That is a many year old obsolete kernel, there's nothing we can do about
that release, sorry. Please try 3.14
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a me
Begin forwarded message:
Date: Mon, 28 Apr 2014 11:06:24 -0700
From: "bugzilla-dae...@bugzilla.kernel.org"
To: "step...@networkplumber.org"
Subject: [Bug 75001] New: belkin USB Ethernet adapter intermittent network issue
https://bugzilla.kernel.org/show_bug.cgi?id=75001
Bug ID:
Hello,
This will be the last post from me on this, at least for a while, out of my
depth with this stuff.
I have Linus' tree up and running with patches recommended by Sarah.
"1. Disable scatter-gather for the ax88179_178a driver when it's under an
xHCI host.
2. Revert the following commits
An update, iommu=pt made no difference in the end the system still came down
eventually.
So i've started from scratch.
Cloned linus' tree
merged "for-usb-linus-3.14" from the xhci tree
applied the latest patch I saw from david on the list:
http://www.spinics.net/lists/linux-usb/msg101747.htm
From: Sarah Sharp
> On Wed, Jan 29, 2014 at 03:48:27PM +, David Laight wrote:
> > I've decided to forward this to the list.
> > If you read further down he says that my patch makes the operation
> > of the ax88179_178a stable - once the system has recognised it properly.
>
> I don't understand
It looks like the issue with being unable to get the device to work at all is
limited to the Asmedia controller.
I plugged a VL800-Q8 based pcie card in and got 117MB/s when sending and
receiving with scp. This is with kernel 3.12.9
I guess it's possible that the ax88179 never worked with the
[Please don't drop Cc'ed people.]
On Thu, Jan 30, 2014 at 10:29:33AM +1100, renev...@internode.on.net wrote:
> The patch did prevent the whole system from crashing but I have to unplug and
> plug something like 20 times to get it not to spit out those error messages.
>
> Even once it is up, it d
On Wed, Jan 29, 2014 at 03:48:27PM +, David Laight wrote:
> I've decided to forward this to the list.
> If you read further down he says that my patch makes the operation
> of the ax88179_178a stable - once the system has recognised it properly.
I don't understand why your patch helped. This
The patch did prevent the whole system from crashing but I have to unplug and
plug something like 20 times to get it not to spit out those error messages.
Even once it is up, it doesn't operate at full gigabit speed and there is
something funky going on. When sending via scp it maxed out at 36MB
I've decided to forward this to the list.
If you read further down he says that my patch makes the operation
of the ax88179_178a stable - once the system has recognised it properly.
David
> -Original Message-
> From: renev...@internode.on.net [mailto:renev...@internode.on.net]
> S
On 1/17/2014 3:43 AM, Felipe Balbi wrote:
Hi,
Hello Felipe,
On Thu, Jan 16, 2014 at 01:58:30PM +0100, Carmelo Amoroso wrote:
I'm one of the maintainer of the STLinux kernel @ST.
Let me clarify the inconvenience occurred about this patches.
We are back-porting some patches from upstream for
Hi,
On Thu, Jan 16, 2014 at 01:58:30PM +0100, Carmelo Amoroso wrote:
> I'm one of the maintainer of the STLinux kernel @ST.
> Let me clarify the inconvenience occurred about this patches.
>
> We are back-porting some patches from upstream for DWC3 driver into
> our 3.4.58 based kernel as our chip
Dear Felipe,
I'm one of the maintainer of the STLinux kernel @ST.
Let me clarify the inconvenience occurred about this patches.
We are back-porting some patches from upstream for DWC3 driver into our
3.4.58 based kernel as our chipsets use this host controller.
The way we do it, is exactly wh
Mauro Carvalho Chehab wrote:
> Clemens Ladisch escreveu:
>> Mauro Carvalho Chehab wrote:
>>> .period_bytes_min = 64, /* 12544/2, */
>>
>> This is wrong (if the driver doesn't install other constraints on the
>> period length, like the USB audio class driver does).
>
> Ok, how should it
Em Thu, 9 Jan 2014 09:29:57 -0200
Mauro Carvalho Chehab escreveu:
> Em Thu, 09 Jan 2014 09:17:13 +0100
> Clemens Ladisch escreveu:
>
> > Mauro Carvalho Chehab wrote:
> > > I'm getting an weird behavior with em28xx, especially when the device
> > > is connected into an audio port.
> > >
> > >
Em Thu, 09 Jan 2014 09:17:13 +0100
Clemens Ladisch escreveu:
> Mauro Carvalho Chehab wrote:
> > I'm getting an weird behavior with em28xx, especially when the device
> > is connected into an audio port.
> >
> >
> > http://git.linuxtv.org/mchehab/experimental.git/blob/refs/heads/em28xx-v4l2-v
Mauro Carvalho Chehab wrote:
> I'm getting an weird behavior with em28xx, especially when the device
> is connected into an audio port.
>
>
> http://git.linuxtv.org/mchehab/experimental.git/blob/refs/heads/em28xx-v4l2-v6:/drivers/media/usb/em28xx/em28xx-audio.c
>
> What happens is that, when
On Wed, 8 Jan 2014, Mauro Carvalho Chehab wrote:
> Hi Hans/Takashi,
>
> I'm getting an weird behavior with em28xx, especially when the device
> is connected into an audio port.
>
> I'm using, on my tests, an em28xx HVR-950 device, using this tree:
>
> http://git.linuxtv.org/mchehab/experi
Hi Hans/Takashi,
I'm getting an weird behavior with em28xx, especially when the device
is connected into an audio port.
I'm using, on my tests, an em28xx HVR-950 device, using this tree:
http://git.linuxtv.org/mchehab/experimental.git/shortlog/refs/heads/em28xx-v4l2-v6
Where the alsa dri
Sent from my BlackBerry wireless device from MTN
-Original Message-
From: thomas.takacs.a...@gmail.com
Date: Sat, 28 Dec 2013 19:46:36
To: Greg KH
Reply-To: thomas.takacs.a...@gmail.com
Subject: Re: Alcatel usb modem
Hi Greg,
I tried to follow these instructions again:
pakeklinux.wordpr
On Fri, Nov 01, 2013 at 05:10:17PM -, David Laight wrote:
> Sarah,
>
> The patch below is a real bug that will hit BE systems, so probably
> ought to be a candidate for 3.12 even though it is late in the cycle.
Thanks for catching this bug. However, it's too late to make it into
3.12. Greg
I recommend this link
http://sevensark.sakura.ne.jp/_73com4_best.youtube.com_net309_.html?cesjtenivaxawe=9462153
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-
;-104
[ 64.49] usb 1-1: hcd_unlink_urb c708e980 fail -1
[ 64.50] usb 1-1: insmod timed out on ep0out len=0/4096
[ 64.50] usb 1-1: ath9k_htc: Firmware - htc_9271.fw download failed
[ 64.51] ath9k_htc: probe of 1-1:1.0 failed with error -22
[ 64.52] usbcore: registe
Begin forwarded message:
Date: Sun, 28 Apr 2013 18:52:29 -0700
From: "bugzilla-dae...@bugzilla.kernel.org"
To: "step...@networkplumber.org"
Subject: [Bug 57251] New: HUAWEI 3G USB modem and abnormal stops
https://bugzilla.kernel.org/show_bug.cgi?id=57251
Summary: HUAWEI 3G USB m
On Fri, Apr 12, 2013 at 08:32:59AM -0700, Stephen Hemminger wrote:
> Created an attachment (id=98391)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=98391)
> zaurus.patch
We need a patch in email form.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb
Begin forwarded message:
Date: Fri, 12 Apr 2013 07:27:18 -0700
From: "bugzilla-dae...@bugzilla.kernel.org"
To: "step...@networkplumber.org"
Subject: [Bug 56521] New: No support of Motorola ZN5 USBnet in zaurus module
https://bugzilla.kernel.org/show_bug.cgi?id=56521
Summary: No
t 03, 2012 12:22 PM
> To: Alexis R. Cortes
> Cc: gre...@linuxfoundation.org; linux-usb@vger.kernel.org;
> linux-ker...@vger.kernel.org; brian.qu...@ti.com; jorge.lla...@ti.com
> Subject: Re: FW: [PATCH] usb: host: xhci: Fix Compliance Mode on
> SN65LVPE502CP Hardware
>
> On T
On Thu, Aug 02, 2012 at 05:11:30PM -0500, Alexis R. Cortes wrote:
> Hi Sarah,
>
> I have rewritten my code following your recommendations. Could you please
> review it and give your comments? If everything is fine I'll proceed to
> generate the patch and submit it.
I have a couple style comment
Hi Sarah,
I have rewritten my code following your recommendations. Could you please
review it and give your comments? If everything is fine I'll proceed to
generate the patch and submit it.
The description of my patch is:
-
From: Konstantin Kletschke <[EMAIL PROTECTED]>
Add new BCD numbers for Nikon D80 Firmware revision v1.10 to the
unusual_devs.h file.
Signed-off-by: Konstantin Kletschke <[EMAIL PROTECTED]>
Signed-off-by: Phil Dibowitz <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
This is a note to let you know that I've just added the patch titled
Subject: USB: storage: Nikon D80 new FW still needs Fixup
to my gregkh-2.6 tree. Its filename is
usb-storage-nikon-d80-new-fw-still-needs-fixup.patch
This tree can be found at
http://www.kernel.org/pub/
From: Konstantin Kletschke <[EMAIL PROTECTED]>
Add new BCD numbers for Nikon D80 Firmware revision v1.10 to the
unusual_devs.h file.
Greg, please apply.
Signed-off-by: Konstantin Kletschke <[EMAIL PROTECTED]>
Signed-off-by: Phil Dibowitz <[EMAIL PROTECTED]>
--
Phil Dibowitz
1 - 100 of 106 matches
Mail list logo
