All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [PATCH 1/9] rt2800: prepare for unification of EEPROM support code
Date: Sun, 8 Nov 2009 18:41:20 +0100	[thread overview]
Message-ID: <200911081841.20717.bzolnier@gmail.com> (raw)
In-Reply-To: <4AF6D2A0.50204@gmail.com>

On Sunday 08 November 2009 15:16:00 Gertjan van Wingerde wrote:
> On 11/08/09 14:38, Bartlomiej Zolnierkiewicz wrote:
> > From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> > Subject: [PATCH] rt2800: prepare for unification of EEPROM support code
> > 
> > * Factor out common code from rt2800[pci,usb]_validate_eeprom()
> >   to rt2800_validate_eeprom().
> > 
> > * Fix interface specific comment in rt2800[pci,usb]_validate_eeprom().
> > 
> > * Enclose interface specific code in rt2800[pci,usb]_init_eeprom()
> >   with rt2x00_intf_is_[pci,usb]() checks.
> > 
> > Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> > ---
> > on top of "rt2x00: Add dynamic detection of eFuse EEPROM in rt2800pci."
> > patch from Gertjan
> > 
> >  drivers/net/wireless/rt2x00/rt2800pci.c |   51 ++++++++++++++++++--------------
> >  drivers/net/wireless/rt2x00/rt2800usb.c |   40 +++++++++++++++----------
> >  2 files changed, 55 insertions(+), 36 deletions(-)
> > 
> 
> <snip>
> 
> > @@ -1234,8 +1241,10 @@ static int rt2800pci_init_eeprom(struct 
> >  	    !rt2x00_rf(&rt2x00dev->chip, RF2750) &&
> >  	    !rt2x00_rf(&rt2x00dev->chip, RF3020) &&
> >  	    !rt2x00_rf(&rt2x00dev->chip, RF2020) &&
> > -	    !rt2x00_rf(&rt2x00dev->chip, RF3021) &&
> > -	    !rt2x00_rf(&rt2x00dev->chip, RF3022)) {
> > +	    (rt2x00_intf_is_usb(rt2x00dev) ||
> > +	     (rt2x00_intf_is_pci(rt2x00dev) &&
> > +	      !rt2x00_rf(&rt2x00dev->chip, RF3021) &&
> > +	      !rt2x00_rf(&rt2x00dev->chip, RF3022)))) {
> >  		ERROR(rt2x00dev, "Invalid RF chipset detected.\n");
> >  		return -ENODEV;
> >  	}
> 
> Can we leave this as-is. There are rt2800usb devices that support these RF chipsets as well (I am now the proud owner of such a device), so there is no
> need to restrict the use of these RF chipsets to just PCI devices.

Please note that the patch doesn't change the current behavior of rt2800usb
and for bisectability reasons I would strongly prefer for it to stay this way.

> So, if we leave this as-is then the EEPROM unification ensures rt2800usb will "support" these RF chipsets as well.

Lets work in incremental fashion -- when there is a need to do such change
lets just do it against current tree and apply it as soon as possible (this
way we won't be spending time on micro-decisions).

IOW just make a post- (or pre-) patch and I'll deal with it.

Thanks.
-- 
Bartlomiej Zolnierkiewicz

  reply	other threads:[~2009-11-08 17:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08 13:38 [PATCH 1/9] rt2800: prepare for unification of EEPROM support code Bartlomiej Zolnierkiewicz
2009-11-08 13:39 ` [PATCH 2/9] rt2800: unify " Bartlomiej Zolnierkiewicz
2009-11-08 13:51   ` Ivo van Doorn
2009-11-08 14:19   ` Gertjan van Wingerde
2009-11-08 13:39 ` [PATCH 3/9] rt2800pci: add missing RF values to rf_vals table Bartlomiej Zolnierkiewicz
2009-11-08 13:51   ` Ivo van Doorn
2009-11-08 14:20   ` Gertjan van Wingerde
2009-11-08 13:39 ` [PATCH 4/9] rt2800usb: reorganize code in rt2800usb_probe_hw_mode() Bartlomiej Zolnierkiewicz
2009-11-08 13:52   ` Ivo van Doorn
2009-11-08 14:20   ` Gertjan van Wingerde
2009-11-08 13:39 ` [PATCH 5/9] rt2800: prepare for rt2800*_probe_hw_mode() unification Bartlomiej Zolnierkiewicz
2009-11-08 13:53   ` Ivo van Doorn
2009-11-08 14:35   ` Gertjan van Wingerde
2009-11-08 17:48     ` Bartlomiej Zolnierkiewicz
2009-11-08 19:09       ` Gertjan van Wingerde
2009-11-08 13:39 ` [PATCH 6/9] rt2800: unify rt2800*_probe_hw_mode() Bartlomiej Zolnierkiewicz
2009-11-08 13:53   ` Ivo van Doorn
2009-11-08 14:36   ` Gertjan van Wingerde
2009-11-08 13:39 ` [PATCH 7/9] rt2800usb: fix RX descriptor naming Bartlomiej Zolnierkiewicz
2009-11-08 13:54   ` Ivo van Doorn
2009-11-08 14:37   ` Gertjan van Wingerde
2009-11-08 13:39 ` [PATCH 8/9] rt2800: add eFuse EEPROM support code to rt2800lib Bartlomiej Zolnierkiewicz
2009-11-08 13:55   ` Ivo van Doorn
2009-11-08 17:34     ` Bartlomiej Zolnierkiewicz
2009-11-08 18:08       ` Ivo van Doorn
2009-11-08 18:13         ` Bartlomiej Zolnierkiewicz
2009-11-08 18:27           ` Ivo van Doorn
2009-11-08 18:32             ` Bartlomiej Zolnierkiewicz
2009-11-08 18:40               ` Ivo van Doorn
2009-11-08 18:47                 ` Bartlomiej Zolnierkiewicz
2009-11-08 19:14                   ` Kalle Valo
2009-11-08 19:21                   ` Bartlomiej Zolnierkiewicz
2009-11-08 19:35                     ` Ivo van Doorn
2009-11-08 19:38                       ` Bartlomiej Zolnierkiewicz
2009-11-08 19:25                   ` Ivo van Doorn
2009-11-08 19:34                     ` Bartlomiej Zolnierkiewicz
2009-11-08 14:38   ` Gertjan van Wingerde
2009-11-08 13:39 ` [PATCH 9/9] rt2800usb: add eFuse EEPROM support Bartlomiej Zolnierkiewicz
2009-11-08 13:56   ` Ivo van Doorn
2009-11-08 14:41   ` Gertjan van Wingerde
2009-11-08 13:50 ` [PATCH 1/9] rt2800: prepare for unification of EEPROM support code Ivo van Doorn
2009-11-08 14:16 ` Gertjan van Wingerde
2009-11-08 17:41   ` Bartlomiej Zolnierkiewicz [this message]
2009-11-08 19:07     ` Gertjan van Wingerde

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=200911081841.20717.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=gwingerde@gmail.com \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.