Send users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."
Today's Topics:
1. Re: [RFC 07/27] rt2800: 5592: fix BBP150 vs BBP105 typo
(Stanislaw Gruszka)
2. Re: [RFC 21/27] rt2800: 5592: add iq calibration
(Stanislaw Gruszka)
----------------------------------------------------------------------
Message: 1
Date: Fri, 15 Mar 2013 18:37:14 +0100
From: Stanislaw Gruszka <[email protected]>
To: Helmut Schaa <[email protected]>
Cc: [email protected]
Subject: Re: [rt2x00-users] [RFC 07/27] rt2800: 5592: fix BBP150 vs
BBP105 typo
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Tue, Mar 12, 2013 at 05:13:20PM +0100, Helmut Schaa wrote:
> On Sat, Feb 23, 2013 at 11:10 AM, <[email protected]> wrote:
> > From: Stanislaw Gruszka <[email protected]>
> >
> > Signed-off-by: Stanislaw Gruszka <[email protected]>
>
> You're going to merge rt5592 into a single patch, right? Because
> this only fixes up an earlier patch of your series.
I'll merge this one and maybe one or two others.
I prefer to post as separate patches as they document in
the changelog, where are the sources we know from how to
program BBP/RF registers
Stanislaw
------------------------------
Message: 2
Date: Fri, 15 Mar 2013 18:41:27 +0100
From: Stanislaw Gruszka <[email protected]>
To: Helmut Schaa <[email protected]>
Cc: [email protected]
Subject: Re: [rt2x00-users] [RFC 21/27] rt2800: 5592: add iq
calibration
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Tue, Mar 12, 2013 at 05:26:06PM +0100, Helmut Schaa wrote:
> > /*
> > + * EEPROM IQ Calibration, unlike other entries those are byte addresses.
> > + */
>
> Are these also byte-addressed in the vendor driver?
Yes, actually vendor driver address whole EEPROM space that way.
> > +static inline u8 rt2x00_eeprom_byte(struct rt2x00_dev *rt2x00dev,
> > + const unsigned int byte)
> > +{
>
> Do we have to consider endianness here? At least rt2x00_eeprom_read
> assumes the eeprom is stored as little endian ...
Byte is just byte, there is no big-endian or little-endian byte :-)
Stanislaw
------------------------------
Subject: Digest Footer
_______________________________________________
users mailing list
[email protected]
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
------------------------------
End of users Digest, Vol 49, Issue 15
*************************************
