Re: [linux-usb-devel] Re: "sr: unaligned transfer" in 2.5.2-pre1

[Matthew Dharm]

--jq0ap7NbKX2Kqbes
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Jens --

Thanks for the info.  It may have been discussed 'here' (tho, this is
crosposted to two different lists), but I've been focused on 2.4 bugs (one
more left!) and hadn't seen this item.

I think for the first 2.5 kernels, we'll o with your 'vaddr' line, but I
think that being able to set highmem_io is a worthwhile thing.  Which leads
me to two questions:
(1) Do the USB HCDs support highmem?  I seem to recall they do, but I'm not
certain.
(2) How do I pass a highmem address to the HCDs?  The URB structures we use
don't seem particularly well-suited for this.

Matt

On Mon, Dec 31, 2001 at 12:51:57PM +0100, Jens Axboe wrote:
> On Sun, Dec 30 2001, Matthew Dharm wrote:
> > If it shouldn't be used, it should be removed from the structure to for=
ce
> > people to change.
>=20
> It will be soonish. Davem has practically finished this already.
>=20
> > This is probably why usb-storage broke, and it wasn't obvious to me what
> > went wrong.
>=20
> It's been discussed here before, both wrt 2.5 and 2.4 with the block
> highmem patches.
>=20
> > So now I guess I need to either (a) compute the address for the USB lay=
er,
> > or (b) figure out how to pass the memory parameters directly, so we can=
 use
> > highmem.
>=20
> If you don't set highmem_io in the scsi host structure, then you can
> always do
>=20
> 	vaddr =3D page_address(sg->page) + sg->offset;
>=20
> --=20
> Jens Axboe
>=20
>=20
> _______________________________________________
> [e-mail]
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

--=20
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.=
net=20
Maintainer, Linux USB Mass Storage Driver

My mother not mind to die for stoppink Windows NT!  She is rememberink=20
Stalin!
					-- Pitr
User Friendly, 9/6/1998

--jq0ap7NbKX2Kqbes
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8MOy/z64nssGU+ykRAjooAJ91v5P78RbRwhl6gowqUrG2yOWWqwCfWqM/
P50gABDJXHwdTLT9tVXMxIA=
=YqRD
-----END PGP SIGNATURE-----

--jq0ap7NbKX2Kqbes--