Most like, you can investigate the issues with VIA chipsets and AMD chipsets 
through Microsoft's or VIA's driver support and Linux kernel v2.4.17. For 
most of the issues I've seen dealing with AMD or VIA-type issues I've found 
a solution or issue crop up in those areas.

I suggest if you are having major issues then get reliable hardware. The DVD 
player world is plagued with this so feel no different. If we have a "buggy" 
ATA-100 or Ultra SCSI-160 driver then we need to stress test the OS on 
quality hardware (IMHO) from the manufacturers or get their support.

I think this is the road less or most often traveled by many of us testing 
applications, OS, or hardware. We need to stress test our drivers with the 
manufacturers to ensure it meets certain criteria before it is "stablized" 
unto the world.

This is just an opinion, but correcting certain testing habits may benefit 
us in the long run. If you look at the iterations of video drivers from the 
video manufacturers then you will see that this is not an easy job (the 
software engineer and hardware engineer are not always in sync with each 
other or not the same person). Then, you have the QA analyst that may not 
run the same test you will do in the real world (high-level server demand 
testing). Basically, what runs normal with under 5-10 users may reach 
critical mass at >25 users.

This is the same for Linux or Microsoft Windows products. You ever buy a 
 >32GB drive and have your OS not able to format it?!?! How about a 180GB 
drive?!? Or try to get your USB port drivers to work properly in Linux?!? We 
all have our issues. So, I hope we can focus on properly researching some of 
the driver and chipset issues we are having and move on to meet the 4.5 
release deadline.

Peace,

Ken
P.S. Only opinions, nothing personal. ;o)

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to