lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <506FDC8C.3030707@realsil.com.cn>
Date:	Sat, 6 Oct 2012 15:23:56 +0800
From:	wwang <wei_wang@...lsil.com.cn>
To:	Borislav Petkov <bp@...en8.de>, Chris Ball <cjb@...top.org>,
	<gregkh@...uxfoundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Phil Turmel <philip@...mel.org>, <sameo@...ux.intel.com>,
	<devel@...uxdriverproject.org>, <linux-kernel@...r.kernel.org>,
	<linux-mmc@...r.kernel.org>, <arnd@...db.de>, <oakad@...oo.com>
Subject: Re: [PATCH v6 0/3] Add modules to support realtek PCIE card reader

于 2012年09月29日 23:29, Borislav Petkov 写道:
> On Sat, Sep 29, 2012 at 09:41:17AM -0400, Chris Ball wrote:
>> On Sat, Sep 29 2012, Borislav Petkov wrote:
>>> So, I think that this driver has seen a bunch of testing and reviewing
>>> and we might start considering upstreaming it. There are a bunch of
>>> laptops integrating those readers and maybe a single three-month-ish -rc
>>> period of testing wouldn't hurt before it appears upstream.
>>>
>>> Now, AFAICT, there is another driver in staging which supports the same
>>> or a subset of the cardreaders this driver does so I don't know what
>>> Realsil want to do with that. Wei?
>>>
>>> And since this driver touches multiple drivers/{mfd,mmc,memstick}
>>> subdirs, maybe akpm would like to merge it? At least I haven't seen any
>>> other maintainers complaining about its design or wanting to take it so
>> I think you've missed the mails -- Alex Dubov has acked the memstick
>> portion, Samuel Ortiz has said he'll push the MFD driver for 3.7,
>> and I've pushed the MMC driver into mmc-next for 3.7.  So, I think
>> we should merge it.  I don't think we need akpm, since there are no
>> build-time dependencies involved.
> Great, all is taken care of then.
>
> Only the staging driver remains, I believe the CONFIG_RTS_PSTOR one. Wei?
>
> Thanks.
>
Hi all:

Sorry for my late reply. I'm on my vacation these days.

At first I want to explain the relationship between the staging driver 
"rts_pstor" with this one here.
Initially, we tried to build a SCSI driver for Realtek PCI-E card 
reader, which has the same architecture and code base with our Windows 
driver. And I pushed rts_pstor to staging tree last year. But Realtek 
PCI-E card reader is not a real SCSI device, which doesn't  understand 
SCSI command at all. So SCSI subsystem won't accept rts_pstor, and I 
can't find a proper subsystem to push it to.  That's why I create this 
series of drivers, which are more compatible with the whole Linux 
architecture.
We are still maintaining the SCSI driver for Realtek card reader, and 
will release the latest source code in the Github in the future.  But 
maybe we won't push it to the staging tree any more.

BR,
Wei WANG

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ