Eric Anholt wrote: > This looks like the classic error of the agp module having been loaded > by the drm because it's required, but agp doesn't probe/attach because > a generic bridge driver has already claimed the agp device.
I doubt that would be a problem as long as it came with a patch to the release scripts so that the agp device was filtered out of the BOOTMFS kernel image. (A quick grep -r for BOOTMFS should show up the sed scripts that turn GENERIC into BOOTMFS in src/release). The 'agp' device isn't likely to hurt anything, is it? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
