From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Date: Mon, 24 Mar 2008 15:29:52 +0000 Subject: Re: [PATCH] 3/3 maple: update bus driver to support Dreamcast VMU Message-Id: <20080324152952.GF2899@logfs.org> List-Id: References: <1206207805.6324.13.camel@localhost.localdomain> <1206209786.6324.41.camel@localhost.localdomain> <20080324033344.GB15872@linux-sh.org> <20080324144647.GC2899@logfs.org> <1206371178.6283.37.camel@localhost.localdomain> In-Reply-To: <1206371178.6283.37.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Adrian McMenamin Cc: Andrew Morton , linux-sh , Greg KH , LKML , Paul Mundt , MTD , dwmw2 On Mon, 24 March 2008 15:06:18 +0000, Adrian McMenamin wrote: >=20 > I don't think I have any alternative here. The problem is that the bus > checks periodically (every HZ ticks but that could be changed) if a > device remains connected to the system by queueing a status command. (If > the status command is replied to with a "No response" then that > indicates to the bus that the device has been removed. Where does this queueing happen? Somewhere in the kernel where we can control it or in hardware? J=C3=B6rn --=20 I don't understand it. Nobody does. -- Richard P. Feynman