Date: Fri, 2 Dec 2011 11:11:22 -0800 From: John-Mark Gurney <jmg@funkthat.com> To: Aleksandr Rybalko <ray@dlink.ua> Cc: freebsd-embedded@freebsd.org Subject: Re: TL-WR1043: switch Message-ID: <20111202191122.GK25601@funkthat.com> In-Reply-To: <20111202164539.fff3ea91.ray@dlink.ua> References: <68ABED76-CB1F-405A-8036-EC254F7511FA@lassitu.de> <3B3DB17D-BF87-40EE-B1C1-445F178E8844@lassitu.de> <86030CEE-6839-4B96-ACDC-2BA9AC1E4AE4@lassitu.de> <2D625CC9-A0E3-47AA-A504-CE8FB2F90245@lassitu.de> <203BF1C8-D528-40C9-8611-9C7AC7E43BAB@lassitu.de> <3C0E9CA3-E130-4E9A-ABCC-1782E28999D1@lassitu.de> <2B8826C7-00C7-4117-B424-4A86F1346DFF@bsdimp.com> <20111130231311.4a154bc5.ray@ddteam.net> <CAJ-Vmon8-yo-UQ%2B81feLT-Yr%2BJimMsEbLHWfd9kZP_s4804%2BtA@mail.gmail.com> <20111202164539.fff3ea91.ray@dlink.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Aleksandr Rybalko wrote this message on Fri, Dec 02, 2011 at 16:45 +0200:
> On Fri, 2 Dec 2011 22:39:32 +0800
> Adrian Chadd <adrian@freebsd.org> wrote:
>
> >> .. erk.
> >>
> >> Well, what shall we do? Create a different driver? Or just enable a
> >> "quirk" or configuration paramater, which allows the device to be
> >> not-quite-i2c?
>
> It's too specific to Realtek, so from one point better to have
> separate driver, but from another point it have i2c EEPROM on same bus.
> So if we want to have access to both, we need quirk.
Not to complicate things, but you could have a custom bus driver that
provides an attachment for the standard i2c bus, and another attachment
for the Realtek part... This custom bus driver would mediate access
between the two...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111202191122.GK25601>