On Mon, 2008-04-21 at 01:22 +0100, Barak A. Pearlmutter wrote: > Thanks for the patch. I will dupload it shortly. > > > In addition, the patch makes sure that the raidutils package > > is built for just i386 and amd64 - it supports only the Adaptec > > DPT ZCR controllers, which can only be found on x86 boards > > as far as I know. > > I'd imagine the Adaptec PCI cards would work on any system with a PCI > bus.
Well, I was thinking about the ZCR cards which are the Zero Channel Raid cards. It means that the motherboard has an Adaptec SCSI controller on board, and there is an extra slot in which you can put the 2000/2005/2010/2015 ZCR controller. These boards are typically x86 boards. There might exist stand-alone PCI cards that you can put into any system with a PCI bus, you're right about that. Didn't think of that. > There is some SPARC-specific stuff in the sources, which I > assume is because that configuration actually exists. Good point. > Perhaps it > would make more sense to just disallow some specific non-amd64 64-bit > architectures. You seem to know more about this i2o 64-bit > cleanliness issue than me: what do you think? I think I was just being short-sighted by assuming all the dpt_i2o cards are of the ZCR variety and that only x86 boards use them. That doesn't have to be true as you pointed out, so if dpt_raidutils builds on all architectures I do not see a reason not to support that. Oh, the i2o 64-bit cleanliness, how do I know about that.. well, I've tried to fix the raidutils code before to actually work in 64-bit mode, and it would be a lot, really a LOT of work. It assumes pointers == long == 32 bits everywhere. Not only that, but the ioctl interface in the kernel also assumes that, so you'd have to put all data buffers for the ioctls in memory < 4G (mmap(MAP_32BIT) ?). I've used the 32 bit package on 64 bit systems for a while now, and recently I found out that it finally is possible to compile 32-bit C++ code in a 64 bit environment .. hence this bugreport. Mike. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
