Re: -STABLE was stable for long time (Re: FreeBSD: Server or DesktopOS?)
Richard Caley wrote: In article [EMAIL PROTECTED], Lefteris Tsintjelis (lt) writes: lt If its a matter of never committed at all (I do have a few doubts on this one) lt then I guess I have no other choice here but -STABLE or at least some other branch lt that is at least maintained. So, which one might that be? If STABLE has become de-facto a development branch, and RELEASE needs to remain rack solid so it can be treated as having had all the pre-release testing on it, making people reluctant to put in any but the safest fixes, perhaps it would be a good idea if there were a system of official patches to RELEASE. These could come with a proviso that they have been tested to STABLE standards, but not to RELEASE standards, but if you absolutely need the fix... I think the best thing is to keep things as simple as possible. That would probably complicate things even further for a not so expert user. I personally think that a fix should always be a fix and should apply to all (-STABLE or -RELEASE or whatever reliable or not branch might that be). It is only a matter if you have been bitten by it or not. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: -STABLE was stable for long time (Re: FreeBSD: Server or DesktopOS?)
I think the best thing is to keep things as simple as possible. But no simpler. I personally think that a fix should always be a fix that is like saying a cure for cancer should be a cure for cancer. Fine. How do you know it is a cure and how do you know what the side effects will be. If life could ever be that simple we wouldn't need _any_ branches. A lot of testing goes into what becomes a release. People using the RELEASE branch have a reasonable expectation that it will have been tested to that standard. That amount of testing can't be done for every fix applied to the STABLE branch. Occasionally there will be a fix which will break something else that no one thought to test. Basicly, you can't have somethign which is stable and which gets fixed quickly, the two aims are in opposition. ^_^ (O O) \_/@@\ \\~~/ ~~ - RJC To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: -STABLE was stable for long time (Re: FreeBSD: Server or DesktopOS?)
Richard Caley wrote: Basicly, you can't have somethign which is stable and which gets fixed quickly, the two aims are in opposition. Something which gets fixed quickly is one definition of stability -- the addition of new features is its opposite. Deciding when a proposed change is defect correction and when it belongs in the next release is the tricky part. Julian Elischer made the point some time ago that it is helpful to continue to support critical fixes to older revs precisely because those folks are using FreeBSD. Pretend we have seats, i.e., customers. Pretend that there are folks out there who aren't hobbyists. From my perspective, the current stable branch is RELENG_4_7, you can go on abusing the language any way you like. OTOH 2.2.8 and 3.5.1 are very stable, just more limited in usefulness. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: -STABLE was stable for long time (Re: FreeBSD: Server or DesktopOS?)
Richard Caley wrote: I think the best thing is to keep things as simple as possible. But no simpler. I personally think that a fix should always be a fix that is like saying a cure for cancer should be a cure for cancer. Fine. It wouldn't be called a cure for a cancer otherwise). How do you know it is a cure and how do you know what the side effects will be. I think the answer is obviously, long time testing and monitoring. If life could ever be that simple we wouldn't need _any_ branches. So lets not make any other sub-branches of branches and patches to comlicate things even further. A lot of testing goes into what becomes a release. People using the RELEASE branch have a reasonable expectation that it will have been tested to that standard. That amount of testing can't be done for every fix applied to the STABLE branch. Occasionally there will be a fix which will break something else that no one thought to test. Basicly, you can't have somethign which is stable and which gets fixed quickly, the two aims are in opposition. But you can have a -STABLE that is reliable and *critical* patches are applied quickly. I believe that this is what mostly this thread is about. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: make release fails
On Mon, Nov 18, 2002 at 11:25:11AM +0200, Ruslan Ermilov wrote: You should have built your current world before attempting to make release. Refer to the release(7) manpage for details. Of course, it is built. Eugene Grosbein To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Fwd: Re: DVD quality problem
great..thanks that fixed it..and it works really well..the only thing i have is that my audio is kinda 'cripsy..i get a few small cracks repeatedly..is there a way to fix this? thanks From: Andrew Thompson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: DVD quality problem Date: Mon, 18 Nov 2002 15:44:56 +1300 alexis georges wrote: Hey guys, i thought i would give a shot to playing a couple of dvd's on my new freebsd machine..so i installed ogle..thats fine..i put in the dvd..launch ogle, goes well..until the movie actually starts..the quality is really choppy..especially when the camera makes a quick movement..i have the nvidia drivers installed..i didn't understand why i would get that choppy video (and crisping in the sound)..so i posted on freebsdforums.org..: Try mplayer. I also get choppy video with ogle but mplayer is fine. mplayer -dvd 1 should do it. Andy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: SiS 900 ethernetcard
Hi there,
I had the same problem about 6 months ago, and someone posted a patch that
did the trick. I have no idea who made the patch so I can't give credit.
It's attached, hope it works.
Jeff Seeman
Technical Instructor
---
FreeBSD-Advocate --- [EMAIL PROTECTED]
---
On Mon, 18 Nov 2002, Willy Offermans wrote:
Dear FreeBSD friends,
I have bought a nice laptop computer (Gericom Masterpiece 25340 XL).
It has an ethernet card inside, based on SiS 900 chip.
During boot, FreeBSD can detect the card, but cannot assign an MAC
address, nor initializing the card. I receive following messages:
sis0: SiS 900 10/100BaseTX port 0xf800-0xf8ff mem 0xe8005000-0xe8005fff irq 4 at
device 4.0 on pci0
sis0: Ethernet address: ff:ff:ff:ff:ff:ff
sis0: MII without any PHY!
device_probe_and_attach: sis0 attach returned 6
Does anybody know to solve this problem?
--
Met vriendelijke groeten,
With kind regards,
Willy
*
W.K. Offermans
Eindhoven University of Technology
Department of Chemical Engineering
Laboratory of Catalysis (SKA)
building ST-W 4.27, PO Box 513
5600 MB Eindhoven, Netherlands
Tel: 0(031) 40 247 37 81
Fax: 0(031) 40 247 50 32
Home: 0(031) 45 544 49 99
e-mail: [EMAIL PROTECTED]
http://www.catalysis.nl
If you are bored playing with Bill Gates' toy, start to work with a real
operating system
Feel free, feel FreeBSD (www.FreeBSD.org)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
*** /sys/pci/if_sisreg.hThu Feb 28 14:39:32 2002
--- if_sisreg.h Mon Jul 1 00:19:19 2002
***
*** 124,129
--- 124,151
#define SIS_EECMD_READ0x180
#define SIS_EECMD_ERASE 0x1c0
+ #define SIS_NOENPHY /* don't use Enhanced PHY Access Register */
+ #ifdefSIS_NOENPHY
+ #define SIS_MII_FRAME_START 0x4000
+ #define SIS_MII_FRAME_OP_READ 0x2000
+ #define SIS_MII_FRAME_OP_WRITE 0x1000
+ #define SIS_MII_FRAME_PMD(phy) ((phy 0x1F) 7)
+ #define SIS_MII_FRAME_REG(reg) ((reg 0x1F) 2)
+ #define SIS_MII_FRAME_LINE_READ 0x
+ #define SIS_MII_FRAME_LINE_WRITE0x0002
+ #define SIS_MII_FRAME_READ(phy, reg) \
+ (SIS_MII_FRAME_START | SIS_MII_FRAME_OP_READ\
+| SIS_MII_FRAME_PMD(phy) | SIS_MII_FRAME_REG(reg) \
+| SIS_MII_FRAME_LINE_READ)
+ #define SIS_MII_FRAME_WRITE(phy, reg) \
+ (SIS_MII_FRAME_START | SIS_MII_FRAME_OP_WRITE \
+| SIS_MII_FRAME_PMD(phy) | SIS_MII_FRAME_REG(reg) \
+| SIS_MII_FRAME_LINE_WRITE)
+ #define SIS_MII_MDC 0x0040
+ #define SIS_MII_MDDIR 0x0020
+ #define SIS_MII_MDIO0x0010
+ #endif/* SIS_NOENPHY */
+
#define SIS_EE_NODEADDR 0x8
#define NS_EE_NODEADDR0x6
*** /sys/pci/if_sis.c Thu Feb 28 14:39:32 2002
--- if_sis.cMon Jul 1 00:11:11 2002
***
*** 475,480
--- 475,483
{
struct sis_softc*sc;
int i, val = 0;
+ #ifdefSIS_NOENPHY
+ int frame_hdr = SIS_MII_FRAME_READ(phy, reg);
+ #endif
sc = device_get_softc(dev);
***
*** 501,506
--- 504,536
sc-sis_rev SIS_REV_635 phy != 0)
return(0);
+ #ifdefSIS_NOENPHY
+ sis_eeprom_idle(sc);
+
+ for (i = (1 15); i; i = 1) {
+ int dataval = SIS_MII_MDDIR;
+ if (frame_hdr i) {
+ dataval |= SIS_MII_MDIO;
+ }
+ CSR_WRITE_4(sc, SIS_EECTL, dataval);
+ sis_delay(sc);
+ CSR_WRITE_4(sc, SIS_EECTL, (dataval | SIS_MII_MDC));
+ sis_delay(sc);
+ }
+
+ for (i = (1 15); i; i = 1) {
+ CSR_WRITE_4(sc, SIS_EECTL, 0);
+ sis_delay(sc);
+ if (CSR_READ_4(sc, SIS_EECTL) SIS_MII_MDIO) {
+ val |= i;
+ }
+ CSR_WRITE_4(sc, SIS_EECTL, SIS_MII_MDC);
+ sis_delay(sc);
+ }
+ CSR_WRITE_4(sc, SIS_EECTL, 0);
+
+ sis_eeprom_idle(sc);
+ #else /* SIS_NOENPHY */
CSR_WRITE_4(sc, SIS_PHYCTL, (phy 11) | (reg 6) | SIS_PHYOP_READ);
SIS_SETBIT(sc, SIS_PHYCTL, SIS_PHYCTL_ACCESS);
***
*** 518,523
--- 548,554
if (val == 0x)
return(0);
+ #endif/* SIS_NOENPHY */
return(val);
}
***
*** 528,533
Re: -STABLE was stable for long time (Re: FreeBSD: Server or DesktopOS?)
I think the answer is obviously, long time testing and monitoring. But you can have a -STABLE that is reliable and *critical* patches are applied quickly. I believe that this is what mostly this thread is about. I refer the honourable gentleman to his above comment `long time testing and monitoring'. How can you have patches applied quickly and also have long time testing necessary to assure everyone that it is not going to break somethign way-over-there. That is my understanding of the difference between RELEASE and STABLE. Releases have intensive testing as an integrated whole. Of course it all comes down to what is considered critical. The bind fixes went in quickly because they filled big holes in many instlations and are relatively isolated. A fix to somethign deep in ther kernel which is not biteing many people? ^_^ (O O) \_/@@\ \\~~/ ~~ - RJC To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: -STABLE was stable for long time (Re: FreeBSD: Server or DesktopOS?)
Richard Caley wrote: A fix to somethign deep in ther kernel which is not biteing many people? This is something for the commiters to decide and not me. http://www.freebsd.org/ This will might help you a bit. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: SiS 900 ethernetcard
On Mon, Nov 18, 2002 at 07:56:25AM -0800, Jeff Seeman wrote: Hi there, I had the same problem about 6 months ago, and someone posted a patch that did the trick. I have no idea who made the patch so I can't give credit. It's attached, hope it works. Jeff Seeman Technical Instructor Any chance to get someone to commit this? IMO it's worth it's place in the tree. JY To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: FreeBSD: Server or Desktop OS?
Green! A. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Fwd: Re: DVD quality problem
If your DVD is ATAPI, make sure that you have DMA enabled. It is off by default. hw.ata.ata_dma and hw.ata.atapi_dma should both be 1. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 From: alexis georges [EMAIL PROTECTED] Date: Mon, 18 Nov 2002 15:37:50 + Sender: [EMAIL PROTECTED] great..thanks that fixed it..and it works really well..the only thing i have is that my audio is kinda 'cripsy..i get a few small cracks repeatedly..is there a way to fix this? thanks From: Andrew Thompson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: DVD quality problem Date: Mon, 18 Nov 2002 15:44:56 +1300 alexis georges wrote: Hey guys, i thought i would give a shot to playing a couple of dvd's on my new freebsd machine..so i installed ogle..thats fine..i put in the dvd..launch ogle, goes well..until the movie actually starts..the quality is really choppy..especially when the camera makes a quick movement..i have the nvidia drivers installed..i didn't understand why i would get that choppy video (and crisping in the sound)..so i posted on freebsdforums.org..: Try mplayer. I also get choppy video with ogle but mplayer is fine. mplayer -dvd 1 should do it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: -STABLE was stable for long time (Re: FreeBSD: Server or DesktopOS?)
A fix to somethign deep in ther kernel which is not biteing many people? This is something for the commiters to decide and not me. Indeed. Isn't the point of this thread, if any, that Marc Fournier was complaining that a patch to the VM system was not put onto the RELEASE branch. As you say, it is for the comitters to decide. I was just saying that it is not really supprising if somethign of this order doesn't make it into RELEASE, since it potentially has such wide repercussions. http://www.freebsd.org/ This will might help you a bit. And a politeness transfusion might help you a bit. ^_^ (O O) \_/@@\ \\~~/ ~~ - RJC To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
