<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test2/sys/isa, branch release/7.2.0_cvs</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F7.2.0_cvs</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F7.2.0_cvs'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/'/>
<updated>2009-05-01T02:51:58Z</updated>
<entry>
<title>Copy releng/7.2 to release/7.2.0 for FreeBSD 7.2-RELEASE.</title>
<updated>2009-05-01T02:51:58Z</updated>
<author>
<name>Ken Smith</name>
<email>kensmith@FreeBSD.org</email>
</author>
<published>2009-05-01T02:51:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=b205d83df7763ca1f099bce5ac12a05862a626c4'/>
<id>urn:sha1:b205d83df7763ca1f099bce5ac12a05862a626c4</id>
<content type='text'>
Approved by:	re (implicit)

This commit was manufactured to restore the state of the 7.2-RELEASE image.
</content>
</entry>
<entry>
<title>MFC: Allow syscons to work on amd64 and i386 without any hints.</title>
<updated>2009-03-19T17:46:51Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2009-03-19T17:46:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=6253d466e01fdb419082de4726fa427549a82a63'/>
<id>urn:sha1:6253d466e01fdb419082de4726fa427549a82a63</id>
<content type='text'>
</content>
</entry>
<entry>
<title>This commit was manufactured by cvs2svn to create branch 'RELENG_7'.</title>
<updated>2007-10-10T16:59:15Z</updated>
<author>
<name>cvs2svn</name>
<email>cvs2svn@FreeBSD.org</email>
</author>
<published>2007-10-10T16:59:15Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=d617d42018994cc58fc6289f978ea2390cac9dcd'/>
<id>urn:sha1:d617d42018994cc58fc6289f978ea2390cac9dcd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>It seems that some i386 mothermoards either do not implement the</title>
<updated>2007-07-27T09:34:42Z</updated>
<author>
<name>David Malone</name>
<email>dwmalone@FreeBSD.org</email>
</author>
<published>2007-07-27T09:34:42Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=9be70a793ef67b216a0a824f3ed6845e9af111ce'/>
<id>urn:sha1:9be70a793ef67b216a0a824f3ed6845e9af111ce</id>
<content type='text'>
day of week field correctly, or they remember bad values that are
written into the day of week field. For this reason, ignore the day
of week field when reading the clock on i386 rather than bailing if
it is set incorrectly.

Problems were seen on a number of platforms, including VMWare, qemu,
EPIA ME6000, Epox-3PTA and ABIT-SL30T.

This is a slightly different fix to that proposed by Ted in his PR,
but the same basic idea.

PR:		111117
Submitted by:	Ted Faber &lt;faber@lunabase.org&gt;
Approved by:	re (rwatson)
MFC after:	3 weeks
</content>
</entry>
<entry>
<title>If clock_ct_to_ts fails to convert time time from the real time clock,</title>
<updated>2007-07-23T09:42:32Z</updated>
<author>
<name>David Malone</name>
<email>dwmalone@FreeBSD.org</email>
</author>
<published>2007-07-23T09:42:32Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=6d8617d42a1988bcc6543ac0c42fa2d998075b50'/>
<id>urn:sha1:6d8617d42a1988bcc6543ac0c42fa2d998075b50</id>
<content type='text'>
print a one line error message. Add some comments on not being able to
trust the day of week field (I'll act on these comments in a follow up
commit).

Approved by:	re
MFC after:	3 weeks
</content>
</entry>
<entry>
<title>Prototype (but functional) Linux-ish /dev/nvram interface to the extra</title>
<updated>2007-06-15T22:58:14Z</updated>
<author>
<name>Peter Wemm</name>
<email>peter@FreeBSD.org</email>
</author>
<published>2007-06-15T22:58:14Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=5915fb72fb9e8f82720f2da747a39e6cdb0b134b'/>
<id>urn:sha1:5915fb72fb9e8f82720f2da747a39e6cdb0b134b</id>
<content type='text'>
114 bytes of cmos ram in the PC clock chip.  The big difference between
this and the Linux version is that we do not recalculate the checksums
for bytes 16..31.

We use this at work when cloning identical machines - we can copy the
bios settings as well.  Reading /dev/nvram gives 114 bytes of data but
you can seek/read/write whichever bytes you like.

Yes, this is a "foot, gun, fire!" type of device.
</content>
</entry>
<entry>
<title>Despite several examples in the kernel, the third argument of</title>
<updated>2007-06-04T18:25:08Z</updated>
<author>
<name>David Malone</name>
<email>dwmalone@FreeBSD.org</email>
</author>
<published>2007-06-04T18:25:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=041b706b2fa9a5d00d1752796abb7af549d5977b'/>
<id>urn:sha1:041b706b2fa9a5d00d1752796abb7af549d5977b</id>
<content type='text'>
sysctl_handle_int is not sizeof the int type you want to export.
The type must always be an int or an unsigned int.

Remove the instances where a sizeof(variable) is passed to stop
people accidently cut and pasting these examples.

In a few places this was sysctl_handle_int was being used on 64 bit
types, which would truncate the value to be exported.  In these
cases use sysctl_handle_quad to export them and change the format
to Q so that sysctl(1) can still print them.
</content>
</entry>
<entry>
<title>When trying to allocate a PnP BIOS memory resource, the code loops trying</title>
<updated>2007-04-17T15:14:23Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2007-04-17T15:14:23Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=90dea4f9a71dc3aea9fbf81b32487fffeb56c2de'/>
<id>urn:sha1:90dea4f9a71dc3aea9fbf81b32487fffeb56c2de</id>
<content type='text'>
to move up the start address until the allocation succeeds.  If the
alignment of the resource was 0, then the code would keep trying the same
request in an infinite loop and hang.  Force the request to always move
start up by at least 1 byte each time through the loop.
</content>
</entry>
<entry>
<title>Partial fix for a bug in rev.1.231.  If suspend/resume clobbers the</title>
<updated>2007-03-05T09:10:17Z</updated>
<author>
<name>Bruce Evans</name>
<email>bde@FreeBSD.org</email>
</author>
<published>2007-03-05T09:10:17Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=d78180f8f5c5f7f7cb275f2e2be866a3e0e72604'/>
<id>urn:sha1:d78180f8f5c5f7f7cb275f2e2be866a3e0e72604</id>
<content type='text'>
RTC state, then it may clobber the RTC index register, so the index
register must be restored before using it to restore control registers
in rtc_restore().

The following problems remain:
- rtc_restore() is only called if pmtimer is configured.  Buggy
  suspend/resumes are more likely to clobber the index register than
  a control register, so pmtimer is more needed than it used to be.
- pmtimer doesn't exist for amd64.
- Restoring of the RTC state may race with rtcintr().  If an RTC
  interrupt is handled before the state is restored, then rtcin(RTC_INTR)
  in rtcintr() may read from the wrong register, so rtcintr() may spin
  forever.  This may be mitigated by the most common state clobbering
  being to turn off RTC interrupts.
</content>
</entry>
<entry>
<title>style(9).</title>
<updated>2007-03-04T04:55:19Z</updated>
<author>
<name>Yoshihiro Takahashi</name>
<email>nyan@FreeBSD.org</email>
</author>
<published>2007-03-04T04:55:19Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=de038d5ffc08e0f550568db8566d079e823c6cc0'/>
<id>urn:sha1:de038d5ffc08e0f550568db8566d079e823c6cc0</id>
<content type='text'>
</content>
</entry>
</feed>
