DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Installation and Upgrading

OpenBSD Installation and Upgrading Installing and upgrading OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 13th March 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Default OpenBSD + BCM4312 [it appears that its BCM4315]

Hello,

I am a long time OpenBSD user and I run it on several servers/desktops.
Last friday I bought Lenovo IdeaPad S10S and I`ve already noticed, that - among some minor glitches - everything works reasonably good.
Everything but not the BCM4312 [probobly] chip-based WLan card.
Actually, it was hard to determine the card chipset, but I figured out other way.
The card is not being detected on on boot. The only interface I get is bge0, which stands for
the ether lan connector, not the actual WLan, which is usually bwi0, or something similar to this.
Anyway - do you have any info? How can I get this running?

Thanks in advance for any help

Last edited by marc; 13th March 2009 at 02:47 PM.
Reply With Quote
  #2   (View Single Post)  
Old 13th March 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,888
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by marc View Post
Anyway - do you have any info? How can I get this running?
When confronted with these types of issues, the best thing to do is play with apropos(1) & peruse the misc@ archives. This reveals that the relevant driver is bwi(4), & the following is what discussion has transpired in the archives:

http://marc.info/?l=openbsd-misc&w=2&r=1&s=bcm4312&q=b

http://marc.info/?l=openbsd-misc&w=2&r=1&s=bwi&q=b

From scanning this information, I would suggest updating the firmware as discussed in the manpage first. If this does not resolve problems, consider installing -current second since development is ongoing, & all improvements will be found in -current first. Thirdly, it has been true with many wireless vendors that they are often less than forthcoming about releasing information to the public, so reverse engineering is a very slow & time consuming process. In the case, patience is more than a virtue.
Reply With Quote
  #3   (View Single Post)  
Old 13th March 2009
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

Unfortunately rev 2 of the BCM4312 requires a firmware that's unsupported.

http://marc.info/?l=openbsd-cvs&m=121993685718267&w=2

Sorry..
Reply With Quote
  #4   (View Single Post)  
Old 13th March 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Default

Hello again,

Thanks for the tips. That makes me doubting no more - there is no real support for this chipset yet. I just wanted to make sure.
Is there any way to check whether it`s rev. 1 or 2? I know for sure that it has been produced in nov/oct 2008.
BTW I`ve tried with OpenBSD snapshot, one of the recent; but it didn`t even bother to detect this chipset.
Not surprisingly it works with linux, in some distros it`s even available 'out-of-the-box', but I`d hate to stuck using linux and that`s not what I want to accomplish.
Reply With Quote
  #5   (View Single Post)  
Old 13th March 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,888
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by marc View Post
Is there any way to check whether it`s rev. 1 or 2?
I don't have your chipset, so I can only guess:
  • Look at the output of dmesg(4). You may find it there.
  • Search the manufacturer's Webpage.
  • As a last resort, determine whether you can find any distinguishing markings on the chip itself.
Lastly, wait. Development on OpenBSD is ongoing, & new additions will be made in time. Again, any new additions made will appear in -current first.
Reply With Quote
  #6   (View Single Post)  
Old 13th March 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Default

Quote:
Look at the output of dmesg(4). You may find it there.
Actually, that was the first thing I did and there is no presence of "bwi*" or whatsoever.
Quote:
Search the manufacturer's Webpage.
Well, yes; but there`s only a linux driver.
BTW do you know of any possibility to run some sort of NDISWRAPPER on top of OBSD?
Quote:
As a last resort, determine whether you can find any distinguishing markings on the chip itself.
It`d be a case with the regular PC-set, but I don`t think dissasembling newly bought laptop [which is on a warranty] is a good thing, so I guess I`ll just wait. In the meantime - FreeBSD/NetBSD/Linux testing ...

Thanks for clearyfying. I appreciate your help.

Last edited by marc; 13th March 2009 at 05:15 PM.
Reply With Quote
  #7   (View Single Post)  
Old 13th March 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,888
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by marc View Post
BTW do you know of any possibility to run some sort of NDISWRAPPER on top of OBSD?
Part of the philosophy of OpenBSD is that no precompiled drivers not written by the OpenBSD developers themselves will ever be integrated into the core system. Such code is not open to inspection & is thus labeled "blobs". The chances of NDISWRAPPER ever being imported into OpenBSD are essentially nil.
Reply With Quote
  #8   (View Single Post)  
Old 13th March 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,888
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by marc View Post
Well, yes; but there`s only a linux driver.
What you want to search for is information relating to chip identification.
Reply With Quote
  #9   (View Single Post)  
Old 13th March 2009
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

If you're positive that you have a BCM4312, then the fact that bwi(4) doesn't attach is indicative of a rev 2 device.

Because the rev 1 chipset is supported, it is thusly identified properly.

A supported card would appear as:
bwi0 at pci? dev ? function 0 "Broadcom BCM4312" rev 0x01: apic ? int ?? (irq ??), address 00:00:00:00:00:00

While an unsupported card would be clearly identified as such:
"Broadcom BCM4312" rev 0x02 at pci? dev ? function 0 not configured

I hope that helps.. as for NDISWRAPER, the answer is no.. that is not available for OpenBSD.
Reply With Quote
Old 13th March 2009
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

I should note, that many newer Broadcom devices in the BCM43xx family are unsupported..

I would avoid that vendor like the plague, but that's just my opinion.
Reply With Quote
Old 13th March 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Default

Unfortunately, I can`t see anything related to this card/chipset, which is weird because I thought it`d show even unsupported HW, but well ...
I know OpenBSD philosophy quite well. It`s just that I didn`t have to configure any WLan on OBSD, so I couldn`t know the right way, or the possibilities.
I`m rather busy now, but on monday I`ll try to set the whole thing up with any firmware I can find and I`ll write about it.
BTW. I didn`t have much choice with this chipset, as it was just integrated with this notebook and there was not much I could do about it.

Thanks, guys.
Reply With Quote
Old 13th March 2009
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

Quote:
Originally Posted by marc View Post
Unfortunately, I can`t see anything related to this card/chipset, which is weird because I thought it`d show even unsupported HW, but well ...
Where are you looking? please post the dmesg here in [code] blocks.. perhaps the issue is elsewhere.

Quote:
Originally Posted by marc View Post
I`m rather busy now, but on monday I`ll try to set the whole thing up with any firmware I can find and I`ll write about it.
I don't understand, there is only 1 firmware package available that's compatible with the OpenBSD driver.. and it does NOT work with rev 2 devices. (...if you're unaware, a driver and a firmware are not the same)

Quote:
Originally Posted by marc View Post
BTW. I didn`t have much choice with this chipset, as it was just integrated with this notebook and there was not much I could do about it.
That's the unfortunate situation with laptops/notebooks, most use MiniPCI or MiniPCI-E cards though.. replacement might be possible, baring any sort of BIOS whitelist.

Quote:
Originally Posted by marc View Post
Thanks, guys.
You're welcome.. but I haven't exactly been able to help you.

Note; most people use the character ' instead of ` for contractions.
Reply With Quote
Old 13th March 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Default

Here`s my dmesg [bsd.mp]:
Code:
OpenBSD 4.5 (GENERIC.MP) #107: Sat Feb 28 00:10:01 MST 2009
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 GHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR
real mem  = 1063677952 (1014MB)
avail mem = 1020207104 (972MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/24/08, BIOS32 rev. 0 @ 0xfdc40, SMBIOS rev. 2.5 @ 0xdf010 (24 entries)
bios0: vendor LENOVO version "14CN38WW" date 10/24/2008
bios0: LENOVO Lenovo
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP APIC HPET MCFG TCPA TMOR APIC BOOT ASF! SSDT SSDT SSDT
acpi0: wakeup devices HDEF(S4) PXS1(S4) PXS2(S4) PXS3(S4) USB1(S4) USB2(S4) USB3(S4) USB4(S4) USB7(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 GHz
cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR
ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (RP01)
acpiprt2 at acpi0: bus 3 (RP02)
acpiprt3 at acpi0: bus 5 (RP03)
acpiprt4 at acpi0: bus 6 (PCIB)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2
acpicpu1 at acpi0: C3, C2
acpitz0 at acpi0: critical temperature 95 degC
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
acpiac0 at acpi0: AC unit offline
acpibat0 at acpi0: BAT0 model "LE30_S" serial   type LION oem "Sanyo"
acpibtn2 at acpi0: LID_
acpivideo at acpi0 not configured
bios0: ROM list: 0xc0000/0xec00! 0xcf000/0x1e00 0xdf000/0x800! 0xe0000/0x1800!
cpu0: unknown Enhanced SpeedStep CPU, msr 0x060f0c2406000c24
cpu0: using only highest and lowest power states
cpu0: Enhanced SpeedStep 1600 MHz (1276 mV): speeds: 1600, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GME Host" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82945GME Video" rev 0x03
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xd0000000, size 0x10000000
inteldrm0 at vga1: apic 1 int 16 (irq 11)
drm0 at inteldrm0
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: apic 1 int 22 (irq 5)
azalia0: codecs: Realtek ALC269
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int 17 (irq 3)
pci1 at ppb0 bus 2
bge0 at pci1 dev 0 function 0 "Broadcom BCM5906M" rev 0x02, BCM5906 A2 (0xc002): apic 1 int 16 (irq 11), address 00:23:8b:26:a0:cb
brgphy0 at bge0 phy 1: BCM5906 10/100baseTX PHY, rev. 0
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int 16 (irq 11)
pci2 at ppb1 bus 3
ppb2 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: apic 1 int 18 (irq 3)
pci3 at ppb2 bus 5
"Broadcom BCM4315" rev 0x01 at pci3 dev 0 function 0 not configured
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 23 (irq 5)
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 19 (irq 10)
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18 (irq 3)
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 1 int 16 (irq 11)
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 1 int 23 (irq 5)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci4 at ppb3 bus 6
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM disabled
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 ignored (disabled)
pciide1 at pci0 dev 31 function 2 "Intel 82801GBM SATA" rev 0x02: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide1: using apic 1 int 19 (irq 10) for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0: <WDC WD1600BEVT-22ZCT0>
wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
ichiic0 at pci0 dev 31 function 3 "Intel 82801GB SMBus" rev 0x02: apic 1 int 19 (irq 10)
iic0 at ichiic0
iic0: addr 0x4a 00=24 01=00 02=4b 03=50 04=50 05=50 06=50 07=50 08=50 09=50 0a=50 0b=50 0c=50 0d=50 0e=50 0f=50 22=4b 40=24 41=00 42=4b 43=50 44=50 45=50 46=50 47=50 48=24 49=50 4a=24 4b=50 4c=50 4d=50 4e=24 4f=50 ee=50 words 00=4f80 01=3000 02=4b00 03=5000 04=5000 05=5000 06=5000 07=5000
spdmem0 at iic0 addr 0x51: 512MB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb4 at uhci3: USB revision 1.0
uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
mtrr: Pentium Pro MTRR support
uvideo0 at uhub0 port 3 configuration 1 interface 0 "BISON Corporation Lenovo EasyCamera" rev 2.00/14.04 addr 2
video0 at uvideo0
umass0 at uhub0 port 5 configuration 1 interface 0 "Generic USB2.0-CRW" rev 2.00/58.87 addr 3
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <Generic-, Multi-Card, 1.00> SCSI0 0/direct removable
sd0: drive offline
ubt0 at uhub2 port 2 "Broadcom Corp BCM2046 Bluetooth Device" rev 2.00/6.01 addr 2
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
Quote:
I don't understand, there is only 1 firmware package available that's compatible with the OpenBSD driver.. and it does NOT work with rev 2 devices. (...if you're unaware, a driver and a firmware are not the same)
Yes, I know the difference between driver and firmware. I just remembered two types of FW packages, well; I must be wrong then.
Quote:
Note; most people use the character ' instead of ` for contractions.
Ahh, sure. I just used to this [I live in Poland - it might be an explanation ].
Reply With Quote
Old 13th March 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,888
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by marc View Post
Code:
pci3 at ppb2 bus 5
"Broadcom BCM4315" rev 0x01 at pci3 dev 0 function 0 not configured
...which points out that we haven't been discussing the correct chip.

Recent traffic in the misc@ archives doesn't indicate that bwi(4) (potentially even in -current...) supports this card:

http://marc.info/?l=openbsd-misc&w=2&r=1&s=bcm4315&q=b

You have three choices at this point:
  • Install -current & see if this resolves the matter for yourself.
  • Wait until OpenBSD 4.5 is released 1 May, & see if it resolves the matter.
  • Submit a problem report. Details for submission can be found at the following:

    http://openbsd.org/report.html

    However, note that the developers will be more interested in reports on -current since from their perspective, OpenBSD 4.4 is quite old at this point. Ultimately, all that matters at this time is what is happening at the head of CVS.
Personally, I suspect you will have to wait.

Last edited by ocicat; 13th March 2009 at 09:15 PM.
Reply With Quote
Old 13th March 2009
marc's Avatar
marc marc is offline
Port Guard
 
Join Date: Jul 2008
Location: Poland
Posts: 25
Thanked 0 Times in 0 Posts
Default

Yes, you're right, somehow I missed this info.
Anyway - I think I'll try with OpenBSD -current, then of course I'll certainly upgrade to release.
Quote:
[BCM]4315 use a different radio than the other broadcom devices supported by bcm(4), and there is currently no support for it.
Considering this, it looks like it's going to get some time to make this working.
Well, maybe - as some folk suggested - there's a time to try FreeBSD+NDIS?

Thanks for your help
Reply With Quote
Old 13th March 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,888
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by marc View Post
Anyway - I think I'll try with OpenBSD -current, then of course I'll certainly upgrade to release.
At this time, OpenBSD 4.5 has already been labeled in CVS. If you install -current now followed by installing 4.5-release later, you will not potentially be getting new functionality. You might be losing functionality by taking this path.
Quote:
Well, maybe - as some folk suggested - there's a time to try FreeBSD+NDIS?
That is your choice to make.
Reply With Quote
Old 14th March 2009
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

From the above dmesg, it appears marc is running 4.5 RELEASE..

As ocicat said, you're using a BCM4315 not a BCM4312.. this chipset isn't supported in the 4.5 release, nor has any work in -CURRENT added the required functionality.

Sorry..
Reply With Quote
Old 14th March 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,888
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by BSDfan666 View Post
From the above dmesg, it appears marc is running 4.5 RELEASE..
No, this dmesg(8) output comes from a snapshot dated 28 February. Tagging occurred around 2 March, so although what was installed is very close to 4.5-release, it isn't.

Nevertheless, BSDfan666 is correct is observing that if this kernel was not able to recognize the BCM4315 chipset, there is very little reason to install 4.5-release once it does become available. Chances are very good that nothing will have changed with respect to BCM4315 support.

The OP should simply follow discussion on misc@ to determine if & when work is completed which will support this particular chip.

Last edited by ocicat; 14th March 2009 at 04:01 AM.
Reply With Quote
Old 14th March 2009
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

Quote:
Originally Posted by ocicat View Post
No, this dmesg(8) output comes from a snapshot dated 28 February. Tagging occurred around 2 March, so although what was installed is very close to 4.5-release, it isn't.
This is contradictory to a post you made on the 28th of February.

http://www.daemonforums.org/showpost...07&postcount=1
Reply With Quote
Old 14th March 2009
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 2,888
Thanked 190 Times in 160 Posts
Default

Quote:
Originally Posted by BSDfan666 View Post
This is contradictory to a post you made on the 28th of February.

http://www.daemonforums.org/showpost...07&postcount=1
This is very off-topic.

You apparently haven't followed the tagging process in much detail in past releases. There are many shades of gray involved in cutting the CD images given that so many developers & platforms are involved along with ports stabilizing. Although the CVS Web interface showed the appearance of OPENBSD_4_5_BASE on 28 February, the increased frequency of snapshots which occurs around tagging continued through the first week in March up until the point where Theo went on vacation. The minor platforms typically see snapshot updates every 30+ days, so the appearance of daily snapshots is quite noticeable.

So quoting myself:
Quote:
Originally Posted by ocicat
This means that most of the functionality to OpenBSD 4.5 has been solidified, & (most likely) only major issues found within the next week will be pushed back into this branch.
I intentionally used language to grant myself wiggle room because I know from experience that tagging doesn't preclude showstopper issues from being checked in after tagging occurs. We saw this when 4.4 was tagged.

So sorry, buddy. No contradiction was made. You should apologize to the OP for hijacking his thread.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 12:48 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick