similar to: [GIT PULL] Remove duplicate COM32 modules

Hi, I just pushed out changes that fix pretty much all the compiler build warnings on the elflink branch. Also, I've added "auto extension" support so that if the user doesn't type the file name extension it will automatically be looked up, e.g. now typing "ls" will execute "ls.c32". The following changes since commit

At boot: prompt, COM32 module calls with full path fails silently. Please let me know if this is not the best fix for it. Also, please forgive me if this is not a bug and I did something wrong on my end. The following changes since commit 2779b713bdd8644ee2b52962ece6daa209b4ba6b: com32: remove duplicate modules (2012-05-22 20:59:51 -0300) are available in the git repository at:

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: b5fe11663b48ca267829b34a65b4133e4e34c993 commit: a256bb8c551310746843ed85de0416ae0571601e [3/11] netdev: pass the stuck queue to the timeout handler config: arm64-allyesconfig (attached as .config) compiler: aarch64-linux-gcc (GCC) 7.5.0 reproduce: wget

Hi, These patches fix some compiler warnings in ldlinux and elflink. I've tried to split the patches out so that they only change one file or one type of problem at once. So, if they do inadvertently introduce any bugs it should at least be easy to bisect to a smallish commit. The following changes since commit 9ded45991b4fc83b40af963feb773ddca2589d74: ldlinux: Parse and store the

Hi, I'd like to ask you what's the best way of generating instruction identifiers which are consistent across independent invocations of the LLVM program. One way would be to use a counter and iterate over all the functions, then all the BBs. But are there any guarantees on the ordering of the functions and BBs in the iteration? In extremis, I can sort the functions after name, but what

On Wed, Sep 8, 2010 at 7:16 PM, Devang Patel <dpatel at apple.com> wrote: > > On Sep 8, 2010, at 5:12 AM, Stefan Bucur wrote: > >> Hi, >> >> I'd like to ask you what's the best way of generating instruction >> identifiers which are consistent across independent invocations of the >> LLVM program. One way would be to use a counter and iterate

It removes a hack from nouveau code which had to detect which region to pass to kick vesafb/efifb. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Eric Anholt <eric at anholt.net> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Thomas Hellstrom <thellstrom at vmware.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com>

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

Hello, I would like to introduce myself as the new Google Summer of Code student for this year. My name is Andr? Ericson and I'm an undergraduate student of Computer Science in Brazil. I will be, with the help of Paulo Alcantara (pcacjr) my mentor, working on implementing Multidisk Support for the Syslinux. For those that are not familiar with the time-line of GSoC, we (students) have until

On Sep 8, 2010, at 5:12 AM, Stefan Bucur wrote: > Hi, > > I'd like to ask you what's the best way of generating instruction > identifiers which are consistent across independent invocations of the > LLVM program. One way would be to use a counter and iterate over all > the functions, then all the BBs. But are there any guarantees on the > ordering of the functions

> Hi there, > > Is there any updated document on COM32 format? > http://www.syslinux.org/doc/comboot.txt > > Is there any updated memory map? > http://www.syslinux.org/wiki/index.php/Memory_Map_(General) > > is there any updated info on Dynamic Module Loading Using the ELF Format? > http://www.syslinux.org/wiki/index.php/GSoC2008_Stefan > > Thanks, >

Greetings! As I have presented in the announcement about the ELF dynamic linker preview earlier this week, one of my tasks now is to reduce the size of the root COM32 module to a minimum, and make the rest of the klibc available as dynamic loadable content. After I studied the linker map output and saw what are the minimal requirements of the dynamic linker itself from the C library (the object

It simplifies nouveau code by removal of detection which region to pass to kick vesafb/efifb. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Eric Anholt <eric at anholt.net> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Thomas Hellstrom <thellstrom at vmware.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com> Cc:

Hello, I have tested a simple thing in two version of Linux and there was a problem when I have used fwmark as a selector for rule lookups. As you can see below on the Slack, the <test> table doesn''t have any label about fwmark. Is there an iproute problem? -------------------------------------- # cat /etc/fedora-release Fedora Core release 2 (Tettnang) # uname -r 2.6.5-1.358 #

Greetings everyone, As my work on SYSLINUX as a Google Summer of Code student is approaching the deadline (only one week left), I would like to publicly announce the availability of a ready-to-test preview of SYSLINUX dynamic module loading support. Currently, SYSLINUX offers support for only loading one module at a time, represented in the COM32 format. This means that whenever another

Greetings everyone, As the official Google Summer of Code 2008 program reached the deadline on August 18, I'd wish to announce the release of the second preview of my work on SYSLINUX, which is also the "GSoC Final Release" (that is, the code I will officially send to Google). You can find about what's new in this release and more in the announcements page, here:

Well, people... I have just merged the "fsc" branch (filesystems in C, largely the work of Liu Aleaxander) and the "elflink" branch (dynamic modules, the work of Claudiu Mihail and Stefan Bucur) together... I haven't tested anything other than it compiling, but it actually does compile. There are almost guaranteed to be issues that I have missed, but well, we get to

Add VIRTIO_F_NOTIFICATION_DATA support for vDPA transport. If this feature is negotiated, the driver passes extra data when kicking a virtqueue. A device that offers this feature needs to implement the kick_vq_with_data callback. kick_vq_with_data receives the vDPA device and data. data includes the vqn, next_off and next_wrap for packed virtqueues. This patch follows a patch [1] by Viktor

On Sun, Apr 02, 2023 at 11:10:34AM +0300, Alvaro Karsz wrote: > Add VIRTIO_F_NOTIFICATION_DATA support for vDPA transport. > If this feature is negotiated, the driver passes extra data when kicking > a virtqueue. > > A device that offers this feature needs to implement the > kick_vq_with_data callback. > > kick_vq_with_data receives the vDPA device and data. > data

On Sun, Apr 2, 2023 at 4:10?PM Alvaro Karsz <alvaro.karsz at solid-run.com> wrote: > > Add VIRTIO_F_NOTIFICATION_DATA support for vDPA transport. > If this feature is negotiated, the driver passes extra data when kicking > a virtqueue. > > A device that offers this feature needs to implement the > kick_vq_with_data callback. > > kick_vq_with_data receives the vDPA