similar to: mysteries of memdisk code

When you add "quiet" to the append line, Syslinux doesn't display the file reading progress anymore. When you use this option to boot an image with MEMDISK, you still get a lot of text. ========================== LABEL mydisk LINUX memdisk INITRD mydisk.img APPEND raw quiet ========================== The following patch makes MEMDISK silent when the quiet keyword is passed to the

Greetings, As a Google Summer of Code student for the SYSLINUX project, I had the chance to learn many interesting things from hpa regarding the internals of SYSLINUX. So besides my main task of implementing ELF modules loading & linking, I decided to put down in the wiki all the information I found concerning SYSLINUX development. In this regard, I have created a special category on the

Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks'' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the

Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers at canonical.com> --- This is mostly just for testing, although it should be safe to apply to nouveau trunk. src/nouveau_dri2.c | 34 +++++++++++ src/nv_driver.c | 163 +++++++++++++++++++++++++++++++++++++++++++++++----- src/nv_type.h | 7 +++ 3 files changed, 191 insertions(+), 13 deletions(-) diff

Here are a few patches adding some missing functions in NvPlatformProbe, which iirc is being used as of xserver 1.13 First patch adds a nouveau_kernel_mode_enabled helper, similar to xf86-video-radeon Second and third use the function in Nv{Pci,Platform}Probe And last one ensures we can still use ZaphodHead and relative head positioning via xorg.conf The coding style may be a bit off, despite my

v2: Fix build against Xservers without Wayland support Don't try to acquire/drop drm master under Wayland Refresh for xserver 1.13 kill-all-direct-access-to-xf86Screens Remove #ifdef soup in favour of xwayland compat header Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers at canonical.com> --- configure.ac | 7 ++ src/Makefile.am |

Hello, I have noticed that Peter wanted to port newlib to syslinux project some time ago. It seems that the porting was not finished. Peter mentioned (http://syslinux.zytor.com/archives/2004-February/003168.html) that sucj job would require a lot of efforts. At the same time newlib is usually regarded as a "highly portable C-library". I am wondering what are the major

Exit with proper message instead of crashing when user forgot to uninstall the proprietary driver. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- src/nv_driver.c | 35 +++++++++++++++++++++++++++++++++++ 1 files changed, 35 insertions(+), 0 deletions(-) diff --git a/src/nv_driver.c b/src/nv_driver.c index f60b6d9..2c953da 100644 --- a/src/nv_driver.c +++

From: Christopher James Halse Rogers <raof at ubuntu.com> Barring some (admittedly significant) missing optimisations? this is reasonably complete, but can't be applied until the Xserver patch has landed, and that needs more work. This demonstrates the approach, however. There's probably some code to be shared with XWayland support, around the output handling (or lack thereof) and

Hello, I would like to access Memdisk (as a RAM disk) from my application in pure protected mode. "Pure" means that I don't' want to have any switches to real mode even if these switches are automatically handled by Memdisk interrupt stubs. The reason is that my application is running on top of Virtual Machine Monitor (VMM). This virtualization layer is quite simple and

Hello, As it is known, Syslinux loads COM32 modules to 0x101000 (the PM IDT is at 0x100000). Unfortunately, in my project this area of memory is already occupied by another program that I need to preserve for a while (specifically, until Syslinux's COM32 module boots up the OS kernel). In other words, I need to load and execute COM32 modules from other than 0x101000 area of memory (for

--- src/nv_driver.c | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/src/nv_driver.c b/src/nv_driver.c index a7cf2dc..6f7fc0e 100644 --- a/src/nv_driver.c +++ b/src/nv_driver.c @@ -780,6 +780,12 @@ NVPciProbe(DriverPtr drv, int entity, struct pci_device *dev, intptr_t data) NVGetPCIXpressChip(dev) : dev->vendor_id << 16 |

I've been working my way through the softphones listed on voip-info over the last few weeks and I've not really found anything to fit the bill. Has anyone had more luck? The environment is a small call centre of 5 users. Operators often need to be able to transfer calls to other operators with different specialties, so the softphone needs to be easy to use and quick to transfer calls.

I've never been able to figure this one out: llvm/lib/VMCore/PassManager.cpp:938: virtual void llvm::PMDataManager::addLowerLevelRequiredPass(llvm::Pass*, llvm::Pass*): Assertion `0 && "Unable to handle Pass that requires lower level Analysis pass"' failed. In the past, I've resolved this by disabling random addRequired calls in the offending Pass, even when

On Jan 28, 2008, at 4:27 PM, David Greene wrote: > I've never been able to figure this one out: > > llvm/lib/VMCore/PassManager.cpp:938: virtual void > llvm::PMDataManager::addLowerLevelRequiredPass(llvm::Pass*, > llvm::Pass*): > Assertion `0 && "Unable to handle Pass that requires lower level > Analysis > pass"' failed. > > In the past,

From experience, an important point that is often forgotten is that the order of declaration of dependencies matter. If you declare that you require pass A, and then pass B, and B doesn't preserve A, you'll get an error like this. Just some advice from having had similar problems in the past. --Owen On Jan 28, 2008, at 9:01 PM, Vikram S. Adve wrote: > > > On Jan 28,

Dear All, I had a similar error back in December; there are a number of email exchanges about it on llvmdev in December 2007; a search through the archives might shed some light on my PassManager does this. If you're updating a pass from pre-LLVM 2.0 to post-LLVM 2.0, you should be aware that the pass manager in LLVM 2.x is used only for scheduling dependent *analysis* passes. If you

Ok, thanks! I'm copying llvmdev again because others had asked about this as well. --Vikram http://www.cs.uiuc.edu/~vadve http://llvm.org/ On Jan 29, 2008, at 4:48 PM, Devang Patel wrote: > > On Jan 29, 2008, at 2:40 PM, Vikram S. Adve wrote: > >> Devang, >> >> I had asked earlier what the message about "lower level analysis >> info" meant.

I was trying to modify the way openssh client (3.9.1p) handles keyboard input (regular input, once the connection is made). I modified the client_process_input function, but it seems that it was never called. I confirmed this with gdb - setting a breakpoint on that function never tripped. Obviously, there must be some other function that openssh uses to read keyboard input, but I can't find

In my controller...this code works def list2 first_name = params[:client][:first_name] @myclients = Client.find(:all, :conditions => ["first_name = :first_name", {:first_name => first_name}]) end this code doesn''t... def list2 first_name = params[:client][:first_name] if first_name searchstring = ''["first_name =