Skip to contentSkip to conversation

Intel x86-64 support merge

PATCH Arjan van de Ven 2 participants 3 messages Feb 18, 2004 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 6 lines · Linux Kernel Mailing List

The ugliest part is probably the swiotlb code. In fact the code for that is not even included, but just reused from IA64. swiotlb implements the PCI DMA API using bounce buffering. I don't like this at all, but there was no other way to support non DAC capable hardware (like IDE or USB) on machines with >3GB. Please redirect all flames for that to the Intel chipset designers.

ehm... so why on earth did Intel cripple this new platform?????

#2 lore raw
Followup to:  <[email protected]>
By author:    Arjan van de Ven <[email protected]>
In newsgroup: linux.dev.kernel
Quoted 12 lines · Linux Kernel Mailing List
Quoted 7 lines

The ugliest part is probably the swiotlb code. In fact the code for that is not even included, but just reused from IA64. swiotlb implements the PCI DMA API using bounce buffering. I don't like this at all, but there was no other way to support non DAC capable hardware (like IDE or USB) on machines with >3GB. Please redirect all flames for that to the Intel chipset designers.

ehm... so why on earth did Intel cripple this new platform?????

Because they were caught by surprise and just hacked the chips they had in the pipeline, presumably.

-hpa

#3 lore raw
Quoted 3 lines · H. Peter Anvin

Because they were caught by surprise and just hacked the chips they had in the pipeline, presumably.

fair enough; I hope this means the next generation has this wart fixed...