b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH] bcmai: introduce AI driver
Date: Fri, 8 Apr 2011 18:56:13 +0200	[thread overview]
Message-ID: <BANLkTin1yyow595tcYveB5fh8q3x+U_GOw@mail.gmail.com> (raw)
In-Reply-To: <op.vtisojsk3ri7v4@arend-laptop>

2011/4/6 Arend van Spriel <arend@broadcom.com>:
> 3. Device identification
>
> The cores are identified by manufacturer, core id and revision in your
> patch. I would not use the revision because 4 out of 5 times a revision
> change does indicate a hardware change but no change in programming
> interface. The enumeration data does contain a more selective field
> indicating the core class (4 bits following the core identifier). I suggest
> to replace the revision field by this class field.

Could you say something more about *class*, please? For my BCM43224 it
seems to be 0x0. WIll check BCM4313 in a moment.

-- 
Rafa?

  parent reply	other threads:[~2011-04-08 16:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 19:57 [RFC][PATCH] bcmai: introduce AI driver Rafał Miłecki
2011-04-05 19:25 ` Rafał Miłecki
2011-04-05 19:29 ` Michael Büsch
     [not found] ` <1302032137.3969.10.camel@Joe-Laptop>
2011-04-05 20:15   ` Rafał Miłecki
2011-04-05 20:25     ` Michael Büsch
2011-04-05 20:50     ` Larry Finger
     [not found] ` <op.vtisojsk3ri7v4@arend-laptop>
2011-04-06 18:02   ` Rafał Miłecki
     [not found]     ` <op.vti9ote53ri7v4@arend-laptop>
2011-04-06 20:40       ` Rafał Miłecki
2011-04-06 20:42         ` Rafał Miłecki
2011-04-06 20:57           ` Michael Büsch
2011-04-06 21:01             ` Rafał Miłecki
2011-04-06 21:08               ` Michael Büsch
2011-04-06 21:12                 ` Rafał Miłecki
2011-04-06 21:20                   ` Michael Büsch
     [not found]                   ` <1302124737.27258.7.camel@dev.znau.edu.ua>
2011-04-06 23:20                     ` Rafał Miłecki
     [not found]                       ` <1302134429.27258.32.camel@dev.znau.edu.ua>
2011-04-07  0:54                         ` Rafał Miłecki
2011-04-07  7:54                           ` Michael Büsch
2011-04-07  9:55                             ` Rafał Miłecki
2011-04-08 16:56   ` Rafał Miłecki [this message]
2011-04-08 17:09     ` Rafał Miłecki
2011-04-08 17:14       ` Rafał Miłecki
     [not found]     ` <op.vtmqm7fw3ri7v4@arend-laptop>
2011-04-08 17:27       ` Rafał Miłecki
     [not found]         ` <op.vtmqujir3ri7v4@arend-laptop>
2011-04-08 17:31           ` Rafał Miłecki
     [not found]   ` <20110410080159.GB2798@ucw.cz>
2011-04-10  8:05     ` Rafał Miłecki
     [not found]       ` <20110410082420.GA1460@localhost.ucw.cz>
2011-04-10  8:30         ` Rafał Miłecki
     [not found]           ` <op.vtpt6v173ri7v4@arend-laptop>
2011-04-10 11:32             ` Rafał Miłecki

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=BANLkTin1yyow595tcYveB5fh8q3x+U_GOw@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).