Date: Sat, 18 Jun 2005 10:35:59 -0500 From: "Wm. Daryl Hawkins" <dhawkins@tamu.edu> To: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-current@freebsd.org, Mike Tancsa <mike@sentex.net> Subject: RE: ichwd fixes / patches Message-ID: <1B77CE3519729C4F86F409F0F3B43A0E069EE6@aspen.ne.tamu.edu>
next in thread | raw e-mail | index | archive | help
Can you give me an idea of what doesn't work with the patches? They've = worked on every system I've tested them on (with the exception of = ICH6... and I don't expect them to work there), but I only have a = limited number of systems to test with. It's definitely something I'll = get fixed if they are broken. Thanks, Daryl > -----Original Message----- > From: owner-freebsd-current@freebsd.org=20 > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of=20 > Dag-Erling Sm=F8rgrav > Sent: Saturday, June 18, 2005 1:15 AM > To: Mike Tancsa > Cc: freebsd-current@freebsd.org > Subject: Re: ichwd fixes / patches >=20 > Mike Tancsa <mike@sentex.net> writes: > > Any chance to commit the patches in the above PR ? I know its not > > ideal, but at least it works where as its currently 100% broken in > > the tree. >=20 > That's the problem: the patch *doesn't* work. I need to sit down with > the docs and painstakingly check everything and figure out why. >=20 > > As to the issue of the ICH6 stuff, looking through the=20 > LINUX lists, it > > seems a lot of ICH6 MBs dont actually hookup the onboard=20 > watchdog for > > some reason. >=20 > I know. The ichwd driver has logic to detect that. >=20 > DES > --=20 > Dag-Erling Sm=F8rgrav - des@des.no >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to=20 > "freebsd-current-unsubscribe@freebsd.org" >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1B77CE3519729C4F86F409F0F3B43A0E069EE6>