Bug 60979

Summary: tridentfb will not compile (uses fp)
Product: [Retired] Red Hat Linux Reporter: Chris Ricker <chris.ricker>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: low Docs Contact:
Priority: low    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-03-25 23:02:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
trident patch to update tridentfb support to 0.70 none

Description Chris Ricker 2002-03-11 08:08:38 UTC 
The tridentfb driver merged in the kernel source is an early version which
cannot be compiled into the kernel:

cc  -D__KERNEL__ -I/usr/src/linux-2.4.18-0.1/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-Wno-unused -pipe -mpreferred-stack-boundary=2 -march=k6  
-DKBUILD_BASENAME=tridentfb  -c -o tridentfb.o tridentfb.c
tridentfb.c:524:2: #error "Floating point maths. This needs fixing before the
driver is safe"
make[3]: *** [tridentfb.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.18-0.1/drivers/video'

If I remember correctly, a more recent version mentioned on linux-kernel fixes
this problem.
Comment 1 Chris Ricker 2002-03-16 08:18:16 UTC 
Created attachment 48724 [details]
trident patch to update tridentfb support to 0.70
Comment 2 Chris Ricker 2002-03-16 08:19:28 UTC 
the attached patch updates tridentfb to the latest version, removing the
floating point issues
Comment 3 Alan Cox 2002-03-25 23:00:33 UTC 
Yes. We could pull that from the newer -ac tree. However it isnt a module we
enable. There are several ways to configure unusable kernels 8)
Comment 4 Arjan van de Ven 2002-03-25 23:04:47 UTC 
Fixed in 2.4.18-0.8; to be in rawhide soon