What's so special about 0xffff EEPROM checksum
I'm looking at driver code in the FreeBSD kernel, and pretty much everywhere I look I see a check for EEPROM checksum. It's always 0x. What is so special about this value 0x? Is this value agreed upon by hardware manufacturers? So basically they have one end slot for data where they put in the last bytes in order to ensure that the checksum is always 0x? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What's so special about 0xffff EEPROM checksum
Where else have you found this check? Hrm. All over the ath code. I guess that's the only place I saw it. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Getting /usr/src/ from SVN directly?
one could also use the -F switch in connection with mergemaster(8). From mergemaster manpage: If the files differ only by VCS Id ($FreeBSD) install the new file. Yes that is exactly what I want, thanks. By the way, are there any other ways that are more preferred to get /usr/src/ than doing what I've done, which is using devel/subversion-freebsd to checkout head into /usr/src/? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Getting /usr/src/ from SVN directly?
I plan on doing some kernel tweaking on CURRENT. If my changes go well I'll submit my changes to one of the devs. I'm used to getting /usr/src/ via supfile using the csup command. I find that it would be a whole lot easier for me to access some sort of anonymous SVN or CVS directly to populate my entire /usr/src/ folder. That way, I would be able to make modifications directly in /usr/src/ and then use commands such as svn status, svn diff, and svn update to view my changes, come up with a patch, and synchronize my source tree [respectively] even after I have local changes. So my question is, is there an SVN or CVS repository to do this sort of thing? Perhaps there is a Handbook page that explains this and I'm just missing it? The end result must be getting the same files under /usr/src/ as when using the CURRENT supfile. So for example: cd /usr/ rm -rf src/ svn checkout svn://some.repos.freebsd.org/src-all/path/to/ ./src ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Getting /usr/src/ from SVN directly?
Use devel/subversion-freebsd though so it expands the $FreeBSD$ RCS tag. I was just gonna say. Doing the plain old SVN checkout of head and mergemaster preworld, I noticed that: *** Displaying differences between ./etc/group and installed version: --- /etc/group 2011-03-22 16:45:05.0 -0700 +++ ./etc/group 2011-03-26 00:32:15.0 -0700 @@ -1,6 +1,6 @@ -# $FreeBSD: src/etc/group,v 1.36 2011/01/28 22:28:12 pjd Exp $ +# $FreeBSD$ # OK will try what you suggest, thanks. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Getting /usr/src/ from SVN directly?
Use devel/subversion-freebsd though so it expands the $FreeBSD$ RCS tag. I just did that. I am afraid however that all of my files in /etc will have a different RCS tag. For example, I got /usr/src/ via SVN directly (head, or CURRENT) and did a mergemaster prebuildworld step, and I get this diff in /etc/group: -# $FreeBSD: src/etc/group,v 1.36 2011/01/28 22:28:12 pjd Exp $ +# $FreeBSD: head/etc/group 218046 2011-01-28 22:28:12Z pjd $ Is there any way that these diffs can be avoided? Is the only real solution to just go through mergemaster file-by-file and install all of the new ones [even though they differ only in this tag]? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Introduce myself and question about getting CURRENT
Hi guys, I'd like to contribute to the FreeBSD community by testing and programming a little in the coming months/years. I'm a mathematician from Berkeley (B.S.), I have been using FreeBSD for about 5 years (on a router and on 2 servers) and I come from a strong programming background (12+ years). I'm also currently involved with some other open source projects such as GtkRadiant, which is a map editor for Quake 3 engine games. An issue in FreeBSD that I'm interested in looking into in the short run is the ath wireless driver situation (I've already contacted Adrian). The two particular issues with the ath driver that I'm currently having may very well already be resolved in CURRENT, so I'm about to test that. Anyhow, first things are first. I need to get CURRENT. So, what is the preferred way to get CURRENT on your system? I'm very familiar with the whole buildkernel/buildworld mechanism and I intend to compile CURRENT from source on a continual basis. The only question I have about this is, is the upgrade 8.2 - CURRENT a supported upgrade that will work fairly well? Or are there some CD image ISOs available for a relatively recent CURRENT? Basically, I'm about to install CURRENT on a new system that will be used for testing and development, and don't know the preferred way to do this. - Nerius Rambetter Landys ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
