mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: hayeswang <hayeswang@realtek.com>
To: "'Bjørn Mork'" <bjorn@mork.no>
Cc: <oliver@neukum.org>, <netdev@vger.kernel.org>,
	"'nic_swsd'" <nic_swsd@realtek.com>,
	<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: RE: [PATCH net-next v2 6/6] r8152: support RTL8153
Date: Tue, 7 Jan 2014 20:35:54 +0800	[thread overview]
Message-ID: <749DBDC9792E47BBA5884BEC7CF2D639@realtek.com.tw> (raw)
In-Reply-To: <87eh4l31or.fsf@nemi.mork.no>

 Bjørn Mork [mailto:bjorn@mork.no] 
> Sent: Monday, January 06, 2014 5:22 PM
> To: Hayeswang
> Cc: oliver@neukum.org; netdev@vger.kernel.org; nic_swsd; 
> linux-kernel@vger.kernel.org; linux-usb@vger.kernel.org
> Subject: Re: [PATCH net-next v2 6/6] r8152: support RTL8153
[...]
> Exactly the same device, but now cfg #1 is active and a 
> different set of
> drivers have bound to the interfaces.  This is possible 
> because none of
> the involved drivers disable the support for this device at 
> build-time.
> Instead they use the available interface descriptors for matching and
> probing supported functions.
> 
> End users will of course normally not go around writing stuff to sysfs
> attributes like this.  Creating an udev rule to select a specific
> counfiguration when the device is plugged is more useful for normal
> usage.

Thanks for your answer. I would study udev rule first.
Does the udev alwayes exist for all Linux system, such as
Android, embedded system, and so on?
 
Best Regards,
Hayes


  reply	other threads:[~2014-01-07 12:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27  2:34 [PATCH net-next 0/6] Support new chip Hayes Wang
2013-12-27  2:34 ` [PATCH net-next 1/6] r8152: move rtl8152_unload and ocp_reg_write Hayes Wang
2013-12-27  2:34 ` [PATCH net-next 2/6] r8152: modify the method of accessing PHY Hayes Wang
2013-12-27  2:34 ` [PATCH net-next 3/6] r8152: change some definitions Hayes Wang
2013-12-27 18:57   ` Francois Romieu
2013-12-27  2:34 ` [PATCH net-next 4/6] r8152: add rtl_ops Hayes Wang
2013-12-27 17:28   ` David Miller
2013-12-27  2:34 ` [PATCH net-next 5/6] r8152: split rtl8152_enable Hayes Wang
2013-12-27  2:37 ` [PATCH net-next 6/6] r8152: support RTL8153 Hayes Wang
2013-12-27 19:08   ` Francois Romieu
2014-01-02  3:22 ` [PATCH net-next v2 0/6] support new chip Hayes Wang
2014-01-02  3:22   ` [PATCH net-next v2 1/6] r8152: move rtl8152_unload and ocp_reg_write Hayes Wang
2014-01-02  3:22   ` [PATCH net-next v2 2/6] r8152: modify the method of accessing PHY Hayes Wang
2014-01-02  3:22   ` [PATCH net-next v2 3/6] r8152: change some definitions Hayes Wang
2014-01-02  3:22   ` [PATCH net-next v2 4/6] r8152: add rtl_ops Hayes Wang
2014-01-02  3:22   ` [PATCH net-next v2 5/6] r8152: split rtl8152_enable Hayes Wang
2014-01-02  3:25   ` [PATCH net-next v2 6/6] r8152: support RTL8153 Hayes Wang
2014-01-02 14:25     ` Bjørn Mork
2014-01-03  2:56       ` hayeswang
2014-01-03  7:49         ` Bjørn Mork
2014-01-06  3:20           ` hayeswang
2014-01-06  9:21             ` Bjørn Mork
2014-01-07 12:35               ` hayeswang [this message]
2014-01-08 18:24                 ` Ben Hutchings
2014-01-02  3:55   ` [PATCH net-next v2 0/6] support new chip David Miller

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=749DBDC9792E47BBA5884BEC7CF2D639@realtek.com.tw \
    --to=hayeswang@realtek.com \
    --cc=bjorn@mork.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=oliver@neukum.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
all inboxes | Powered by JetHome®