search for: osdev

...he code is already using srand()/rand() then > there is no reason to assume somehow the benchmark is worse if it > always used the FreeBSD one, say, as opposed to a platform specific > one. +1 There are a couple of example implementations here which are only a few lines long: http://wiki.osdev.org/Random_Number_Generator -Hal > > - Daniel > > > > > > > > I think that, in this particular case, having bugs in GCC is far less > problematic than assuming fixed outputs. > > > I've tried USE_REFERENCE_OUTPUT := 0 on the Makefile, but t...

On Tue, Mar 12, 2013 at 10:23 AM, Renato Golin <renato.golin at linaro.org>wrote: > On 12 March 2013 16:48, Daniel Dunbar <daniel at zuster.org> wrote: > >> The former mode is historically what the test suite did, the latter mode >> is substantially faster (and independent of bugs in the native CC). >> > > Yes, I agree this is better for many cases, but

On 05/03/2016 02:31 AM, Thomas Schmitt via Syslinux wrote: > Hi, > > John Lewis wrote: >> https://help.ubuntu.com/community/LiveCDCustomizationFromScratch >> >> The show stopper for me was the mkisofs because the closest command I >> had available was xorrisofs and I think a switch was different. > If you have questions about xorrisofs, then just ask me. :))

...en the machine instruction is emitted Does this seem feasible? Does the LLVM x86 backend currently have the capability of adding instruction prefixes and could someone please point out where I should look in the code for it? Thanks, Scott A. Carr PhD Student Purdue University CS [1] http://wiki.osdev.org/X86-64_Instruction_Encoding#Operand-size_and_address-size_override_prefix

For example something like STARTUP ( http://wiki.osdev.org/Linker_Scripts#STARTUP) is not accepted by the LLVM LLD. :-/ On Wed, Apr 20, 2016 at 9:08 PM, Sky Flyer <skylake007 at gmail.com> wrote: > Yeah I found it, that's nice. Thanks a milion. > Could you please tell me how can I specify my bootstrap (startup code) in > the linkin...

On 12 March 2013 19:21, Hal Finkel <hfinkel at anl.gov> wrote: > +1 > > There are a couple of example implementations here which are only a few > lines long: > http://wiki.osdev.org/Random_Number_Generator I was going to rant about the quality of simple LCGs but it seems that *all* standard implementations rely on that, so the argument of using a standard library against a one-liner is void. ;) Now, on to the practical issues: is there a place where this can be added on...

.... The options reflect a long tradition of program mkisofs and the winded road of boot firmware entry points in ISO 9660 filesystems. So one cannot expect to find much of a common system in them. > there doesn't seem to > exist a hello word like exercise that is simple and predictable. OSDev.org tries to provide such examples. Begin to read here: http://wiki.osdev.org/El-Torito http://www.syslinux.org/wiki/index.php?title=ISOLINUX for booting from optical media and then go on to http://www.syslinux.org/wiki/index.php?title=Isohybrid for learning about enhancing the ISO for US...

Hi, me: > > Please enable editing. Gene Cumm: > Done. Thanks. I have now edited http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#USB-Miscellaneous ------------------------------------------------------------ Next i'll try to develop a user oriented hint for SYSLINUX#Creating_a_Bootable_Disk which takes into respect the opinions of Ady, Mattias, me, and of any

...isplay has no VGA memory section at offset > > 0x400 [1]. By writing to this register Linux can create a write to > > unassigned memory which depending on machine and architecture can result > > in a store fault. > > > > I don't see any reference to this address at OSDev [2] or in the Bochs > > source code. > > > > Removing this write still allows graphics to work inside QEMU with > > the bochs-display. > > It's not that simple. The driver also handles the qemu stdvga (-device > VGA, -device secondary-vga) which *does* need the...

...isplay has no VGA memory section at offset > > 0x400 [1]. By writing to this register Linux can create a write to > > unassigned memory which depending on machine and architecture can result > > in a store fault. > > > > I don't see any reference to this address at OSDev [2] or in the Bochs > > source code. > > > > Removing this write still allows graphics to work inside QEMU with > > the bochs-display. > > It's not that simple. The driver also handles the qemu stdvga (-device > VGA, -device secondary-vga) which *does* need the...

I''ve been looking into the performance impact of NCQ. Here''s what i found out: http://blogs.sun.com/erickustarz/entry/ncq_performance_analysis Curiously, there''s not too much performance data on NCQ available via a google search ... enjoy, eric

Running an mmap-intensive workload on ZFS on a X4500, Solaris 10 11/06 (update 3). All file IO is mmap(file), read memory segment, unmap, close. Tweaked the arc size down via mdb to 1GB. I used that value because c_min was also 1GB, and I was not sure if c_max could be larger than c_min....Anyway, I set c_max to 1GB. After a workload run....: > arc::print -tad { . . . ffffffffc02e29e8

...86 backend currently have > the capability of adding instruction prefixes and could someone > please point out where I should look in the code for it? > > Thanks, > Scott A. Carr > PhD Student > Purdue University CS > > [1] > http://wiki.osdev.org/X86-64_Instruction_Encoding#Operand-size_and_address-size_override_prefix > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org> > http://lists.llvm.org/cgi-bin/mailman/l...

I was trying to simply test bandwidth that Solaris/ZFS (Nevada b63) can deliver from a drive, and doing this: dd if=(raw disk) of=/dev/null gives me around 80MB/s, while dd if=(file on ZFS) of=/dev/null gives me only 35MB/s!?. I am getting basically the same result whether it is single zfs drive, mirror or a stripe (I am testing with two Seagate 7200.10 320G drives hanging off the same interface

...2 characters of 16 bit each.) > # Could anyone give me an example to do this same thing, using > # `genisoimage', or `xorriso'? The options used in your example (as well as R, -r, -J) are supported by genisoimage and by "xorriso -as mkisofs", too. See also http://wiki.osdev.org/El-Torito#Example_of_ISO_Filesystem_Production_Run_for_BIOS genisoimage is a clone of mkisofs as of 2006, enhanced by several new options to serve the needs of Debian CD image production. xorriso is not a mkisofs clone, but offers a compatibility mode. hpa wrote: > xorriso uses a differe...

FYI, http://www.informit.com/articles/article.aspx?p=1215438 -Rajika -- http://wso2.org/ http://llvm.org/ http://www.osdev.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090405/79ddb769/attachment.html>

On Mar 12, 2013, at 12:48, Renato Golin <renato.golin at linaro.org> wrote: On 12 March 2013 19:21, Hal Finkel <hfinkel at anl.gov> wrote: > +1 > > There are a couple of example implementations here which are only a few > lines long: > http://wiki.osdev.org/Random_Number_Generator I was going to rant about the quality of simple LCGs but it seems that *all* standard implementations rely on that, so the argument of using a standard library against a one-liner is void. ;) Now, on to the practical issues: is there a place where this can be added on...

...value of %ecx and compensate the additional bytes by e.g. shortening the error message. (All together must fit into 432 bytes.) It seems to me that the %si value is expected to be inherited from the run of the previous MBR code, which decided about the partition to be chainloaded. http://wiki.osdev.org/MBR_%28x86%29 "Typical MBR bootstrap code will do the following: [...] * [...] load the Volume Boot Record (VBR, the "bootsector" of the bootloader) from the beginning of the selected partition * set DS:SI pointing to the selected partition table entry * jump to 0x7c00 (wi...

...section at offset > > > 0x400 [1]. By writing to this register Linux can create a write to > > > unassigned memory which depending on machine and architecture can result > > > in a store fault. > > > > > > I don't see any reference to this address at OSDev [2] or in the Bochs > > > source code. > > > > > > Removing this write still allows graphics to work inside QEMU with > > > the bochs-display. > > > > It's not that simple. The driver also handles the qemu stdvga (-device > > VGA, -device s...

...-r for Rock Ridge names and file attributes. > This will make appear the files with their original names, as in > ISO_root, when the ISO filesystem gets mounted on unix-like systems. > (Up to 255 characters of 8 bit each. E.g. UTF-8.) > > Thank you for this ^ . > > http://wiki.osdev.org/El-Torito#Example_of_ISO_Filesystem_Production_Run_for_BIOS > And this ^. man xorrisofs > http://www.gnu.org/software/xorriso/man_1_xorrisofs.html > > Some of these options are add-ons which you will not find > in mkisofs. Vice versa, several mkisofs options are not supporte...