> Doing it with a loopback like interface at a higher level is the much
> saner operation - I understand why Martin removed the byteswap support,
> and agree with it 100%. It just didn't make any sense from a driver
> standpoint.
We need to support partitioning on loopback devices in that case.
> The only reason byteswapping exists is a rather historical one: Linux did
> the wrong thing for "insw/outsw" on big-endian architectures at one point
> (it byteswapped the data).
A small number of other setups people wired the IDE the quick and easy
way and their native format is indeed ass backwards - some M68K disks and
the Tivo are examples of that. Interworking requires byteswapping and the
ability to handle byteswapped partition tables.
Given the ability to see partitions on loop devices all works out I think
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Apr 23 2002 - 22:00:15 EST