On 23/09/2011, at 11:39, Fbsd8 wrote:
> I have installed 9.0 bata2 from cd and the net. In both cases after the
> completion of the install and rebooting, the bsdinstall scripts still remain
> on the new installed system. If I interpret the code logic correctly,
> bsdinstall can ONLY be used fo
On Wed, Sep 21, 2011 at 08:26:47AM + I heard the voice of
Thomas Mueller, and lo! it spake thus:
>
> I don't think there is any particular advantage in aligning GPT
> partitions on 1 MB boundaries.
No, but it's bg, and rund! (http://dilbert.com/fast/1994-03-24/)
It's a nice round nu
On 23 September 2011 10:09, Fbsd8 wrote:
> I have installed 9.0 bata2 from cd and the net. In both cases after the
> completion of the install and rebooting, the bsdinstall scripts still remain
> on the new installed system. If I interpret the code logic correctly,
> bsdinstall can ONLY be used fo
On Sat, September 17, 2011 11:02, Tijl Coosemans wrote:
> On Wednesday 14 September 2011 05:59:05 Nenhum_de_Nos wrote:
>> I just installed BETA2 on WD notebook disk:
>>
>> ada0 at ata2 bus 0 scbus1 target 0 lun 0
>> ada0: ATA-8 SATA 2.x device
>> ada0: 150.000MB/s transfers (SATA, UDMA5, PIO 8192
I have installed 9.0 bata2 from cd and the net. In both cases after the
completion of the install and rebooting, the bsdinstall scripts still
remain on the new installed system. If I interpret the code logic
correctly, bsdinstall can ONLY be used for an original install. It's not
intended by de
hail again,
has anyone seen these:
ACPI Error: Method parse/execution failed [\\_SB_.PCI0.LPC_.SMBR] (Node
0xfe00024af9c0), AE_AML_INFINITE_LOOP (20110527/psparse-560)
ACPI Error: Method parse/execution failed [\\_SB_.PCI0.LPC_.INIT] (Node
0xfe00024afa00), AE_AML_INFINITE_LOOP (20110527/p
TB --- 2011-09-22 21:50:00 - tinderbox 2.7 running on freebsd-current.sentex.ca
TB --- 2011-09-22 21:50:00 - starting HEAD tinderbox run for i386/i386
TB --- 2011-09-22 21:50:00 - cleaning the object tree
TB --- 2011-09-22 21:50:47 - cvsupping the source tree
TB --- 2011-09-22 21:50:47 - /usr/bin/c
The current firmware(9) mechanism might work for you. The QLogic FC/SCSI
cards in FreeBSD use that for loading firmware images to download to the
cards, albeit to just load and reset, to update flash.
"not to update flash" (locations in flash where to put firmware are not
documented by Ql
The current firmware(9) mechanism might work for you. The QLogic FC/SCSI
cards in FreeBSD use that for loading firmware images to download to the
cards, albeit to just load and reset, to update flash. This allows the
drivers themselves to request updates.
Note that the root filesystem has to
if (cold)
DELAY()
else
pause()
On Sep 22, 2011, at 11:55 AM, David Somayajulu wrote:
> It appears that the pause() function cannot be used in driver functions which
> are invoked early in the boot process. Is there is a kernel api which a
> device driver can use to determine whether to use paus
On Thursday 22 September 2011 19:55:23 David Somayajulu wrote:
> It appears that the pause() function cannot be used in driver functions
> which are invoked early in the boot process. Is there is a kernel api
> which a device driver can use to determine whether to use pause() or
> DELAY(), for dela
It appears that the pause() function cannot be used in driver functions which
are invoked early in the boot process. Is there is a kernel api which a device
driver can use to determine whether to use pause() or DELAY(), for delays which
are say greater than 10hz - may be even 1 hz ?
Cheers,
Dav
Hi All,
1. What is the current recommended method for upgrading firmware for HBAs?
2. Is there a mechanism wherein the firmware binary can be provided as a
separate file, which is then made accessible to the corresponding device
driver during device initialization?
3. Is the
13 matches
Mail list logo
