linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Anton Fedorov" <datacompboy@call2ru.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: ftdi_sio usb-serial driver and hotplug
Date: Fri, 27 Feb 2009 15:49:59 +0000	[thread overview]
Message-ID: <696cb67878af48be224687d8d64f0160.squirrel@webmail.call2ru.com> (raw)
In-Reply-To: <559911452.20090224133820@call2ru.com>


В письме от Срд, 25 Фев 2009, 19:25 Kay Sievers пишет:
> On Wed, Feb 25, 2009 at 14:12, Anton Fedorov <datacompboy@call2ru.com> wrote:
>>
>> В письме от Втр, 24 Фев 2009, 22:16 Kay Sievers пишет:
>>>>   I have tried to setup udev, by putting into /etc/udev/rules.d/
>>>>   file z99_ftdi.rules with contents:
>>>> DRIVER="ftdi_sio", SUBSYSTEM="usb-serial", ATTR{latency_timer}="1"
>>>>   test of rules show that it should correctly write on connection,
>>>>   but after reconnect of device it doesn't have latency_timer
>>>>   changed -- it still have 16 latency set :(
>>> Try DRIVERS=, it should work here, because the parent device is also
>>> created by the same driver. The driver value may not be set at the
>>> time the event is processed, because the driver is binding to the
>>> device not already bound.

Sorry for wrong answer last time -- instead of "reply to list" clicked "reply
private" :) yes, you right -- using "DRIVERS=" fixed problem, now latency
correctly set up.
Many thanks!

But why that difference? udevinfo --attribute-walk shows DRIVER="" related to
device, and  http://reactivated.net/writing_udev_rules.html says "you cannot
mix-and-match attributes from multiple parent devices - your rule will not
work".


-- 
Regards,
Anton Fedorov
Call2ru service


  parent reply	other threads:[~2009-02-27 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24  7:38 ftdi_sio usb-serial driver and hotplug Anton Fedorov
2009-02-24 16:16 ` Kay Sievers
2009-02-27 15:49 ` Anton Fedorov [this message]
2009-02-27 15:52 ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=696cb67878af48be224687d8d64f0160.squirrel@webmail.call2ru.com \
    --to=datacompboy@call2ru.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).