search for: mjg

...The IAXy, 200 and, softphone will be used by less phone dependant types) but what I can't figure out from the Wiki is if it's possible to have the ZAP lines notify for the outbound lines so we can see how many lines are in use. My configuration looks something like this: sip.conf: [mjg] type=friend username=mjg context=sip callerid="Masuo" <6001> secret=**** host=dynamic defaultip=199.242.227.227 canreinvite=no mailbox=6001 subscribecontext=sip [pjf] type=friend username=pjf context=sip callerid="Patrick" <6003> secret=**** host=dynamic defaultip=...

Hi, Ady wrote: > If a specific BIOS' CHS/LBA translations cannot cope with the above, it > is no surprise that we get some mess, somewhere. Currently my suspicion is that the isohdpfx.S code simply mishandles the two conversion factors which it correctly got from BIOS call INT 13H AH 8. > Boot System ID : First : Last : Relative : Number of: > Flag

Hi, Ady wrote: > In the last few years, ISOLINUX has received very low attention, both > upstream and downstream. Nevertheless the well established Linux distros use it for their ISOs. Most have adopted mjg's isohybrid --uefi layout. Only SuSE does it different. So for me with my xorriso hat on, ISOLINUX is as an important partner as is GRUB. > So I' am about to (attempt to) provide a > generic suggestion for you (and for interested users / developers). > [...] > What I would s...

...odify the backlight control registers directly. This patch adds support for determining whether the registers appear to be in use, and if so registers a kernel backlight device to control them. The backlight can then be controlled via existing userspace tools. Signed-off-by: Matthew Garrett <mjg at redhat.com> diff --git a/linux-core/Makefile.kernel b/linux-core/Makefile.kernel index 1e03347..0bea35d 100644 --- a/linux-core/Makefile.kernel +++ b/linux-core/Makefile.kernel @@ -22,6 +22,7 @@ i810-objs := i810_drv.o i810_dma.o nouveau-objs := nouveau_drv.o nouveau_state.o nouveau_fifo....

...status would be improved in the (near) future. At least we need to put some tangible beef to the explanation of isohybrid.c option --uefi in the wiki. It would be helpful to get a hint from hpa, about what situation shall be described in the isohybrid wiki. Where any plans or decisions made when mjg implemented --uefi ? At that time it must have been obvious that Fedora Live CD would boot GRUB2 via EFI and not SYSLINUX. Have a nice day :) Thomas

> Hi, > > Ady wrote: > > http://repo.or.cz/syslinux.git/tree/HEAD:/diag > > "handoff.bin > > This does not look like it would tell much of the properties in question. > Nevertheless its print functions might be of interest for an isohybrid > diagnostic MBR. > > > > and at least 2 geodsp*.{bin,img(gz)} > > I am now reading >

Hello, Sorry I know this might be the wrong group to ask this in but I have been having a lot of trouble switching off the nvidia chip in my Macbook Pro 9,1. I have tried numerous things but there is a lot of flawed documentation out there on this. I have a pile of info (dmesg, kernel configs and etc) that I would like to submit as a bug reports but no clear place to send it. Who maintains the

Hi, Ady wrote: > so, why the original isohybrid image from Debian and many other > isohybrid images have mostly (but not all) "00s" in place of the "90s"? That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. * Fedora has it with EFI FAT filesystem in one partition and a HFS filesystem in another partition. * Debian and Ubuntu have it only for the EFI FAT partition. * ArchLinux 2016 has no APM. * Gentoo 2016 va...

...etting the Head and Sector parameters > correctly for isohybrid, so they still use "64/32" while distributing > images of several GBs each. That's what utils/isohybrid.c does. After 8,422,686,720 bytes, even the range of 255/63 is exhausted. > I guess a word from hpa or mjg could help Yeah. I wonder what hpa thinks about my suspicion. But Martin should be qualified too, to judge my findings and to produce a corrected isohdpfx.bin for testing, if he thinks that i am right. --------------------------------------------------------------------- We still have to find o...

We want to be able to guarantee the location of the allocated buffer object if we're going to be able to reliably allocate the existing framebuffer at startup. Add an argument to do so and pass that through to the ttm core. Signed-off-by: Matthew Garrett <mjg at redhat.com> --- drivers/bcma/main.c | 1 - drivers/gpu/drm/nouveau/nouveau_bo.c | 8 +++++++- drivers/gpu/drm/nouveau/nouveau_channel.c | 2 +- drivers/gpu/drm/nouveau/nouveau_drv.h | 4 ++-- drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- driv...

...uture. > > At least we need to put some tangible beef to the explanation of > isohybrid.c option --uefi in the wiki. > > It would be helpful to get a hint from hpa, about what situation shall > be described in the isohybrid wiki. > > Where any plans or decisions made when mjg implemented --uefi ? > At that time it must have been obvious that Fedora Live CD would boot > GRUB2 via EFI and not SYSLINUX. > I'm afraid I don't actually know a whole lot. At the time, I didn't have any system on which I could attempt to test this. I do now, but haven...

...ce of less than 1GB should be preferred. BTW, many distros are still not setting the Head and Sector parameters correctly for isohybrid, so they still use "64/32" while distributing images of several GBs each. I am not discarding a bug in isohybrid either. I guess a word from hpa or mjg could help, but I wouldn't count on that. Regards, Ady

Hello, By having a look at 'drivers/platform/x86/apple-gmux.c', it seems its author is Seth Forshee <seth.forshee at canonical.com>. Other main contributors are Andreas Heider <andreas at meetr.de>, and Matthew Garrett <mjg at redhat.com>, among others. Pierre Moreau On 11:58 PM - Jul 26 2014, Evan Foss wrote: > Hello, > > Sorry I know this might be the wrong group to ask this in but I have > been having a lot of trouble switching off the nvidia chip in my > Macbook Pro 9,1. I have tried numerou...

...previous image. The 64kb link to this image is at http://77.110.8.68/64kb-1.img So far both images will boot in EFI mode using vbox but I yet to test with usb booting or optical media. I will have some of those test results on my next email along with the hardware used to boot each image. F.Y.I mjg uses a modified mkisofs not genisoimage, this can be seen at https://git.fedorahosted.org/cgit/pungi.git/tree/src/pypungi/__init__.py#n1472 Anyways, I hope this data helps with getting to the bottom of things, I will be around if you need further data and if you want to test the actual images let...

...e Apple Partiton Map of xorriso and isohybrid.c alike. Do Macs recognize it ? > Using GPT and creating fresh protective MBR. Let's hope that it does not write that MBR into the ISO. > Warning! Main partition table overlaps the first partition by 64 blocks! This is a consequence of the mjg multi-hybrid layout, which prescribes nested partitions. There is a school of thought which emphasizes that partitions should not be nested (see the results of GRUB2's grub-mkrescue with EFI support). ------------------------------------------------------------ If you really rely on Apple Par...

...gt; correctly for isohybrid, so they still use "64/32" while distributing > > images of several GBs each. > > That's what utils/isohybrid.c does. > > After 8,422,686,720 bytes, even the range of 255/63 is exhausted. > > > > I guess a word from hpa or mjg could help > > Yeah. I wonder what hpa thinks about my suspicion. He has an explicit carbon copy, cc, of this mailinglist post. > But Martin should be qualified too, to judge my findings and to produce > a corrected isohdpfx.bin for testing, if he thinks that i am right. Martin pos...

...this a GPT partition table? > Yes/No? yes > Error: Both the primary and backup GPT tables are corrupt. That's because of the nested GPT partitions, i assume. The complaints of parted are justified. But the deviations from GPT specs and MBR traditions are necessary and intentional. (The mjg BIOS+EFI+Mac isohybrid layout is king in booting. Otherwise one should not look at it while reading the specs.) In any case, a non-EFI BIOS should not see anything noteworthy in the GPT equipment. Just some bytes in some blocks of the medium. > I assume dd will encounter a write error and ex...

> Hi, > > Ady wrote: > > so, why the original isohybrid image from Debian and many other > > isohybrid images have mostly (but not all) "00s" in place of the "90s"? > > That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. > Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. > > * Fedora has it with EFI FAT filesystem in one partition and a HFS filesystem > in another partition. > * Debian and Ubuntu have it only for the EFI FAT partition. > * ArchLinux 201...

...ot;$iso" bs=1 count=8 | od -t x1 must report 0000000 45 52 08 00 00 00 90 90 (... or the start bytes of isohdpfx.bin without APM patched in: 0000000 33 ed 90 90 90 90 90 90 But then one would not need to preserve them. ) Else the old MBR is supposed to be older than the preparation for mjg layout on 2011-08-24: https://git.kernel.org/pub/scm/boot/syslinux/syslinux.git/commit/mbr/isohdpfx.S?id=2c3a24e5f4b807ec31595227afa59a818c060ca9 Thus it would be dangerous to let its first 32 bytes survive. After all they get executed as x86 instructions when BIOS starts the MBR. As long as no...

Hi, Gene Cumm wrote: > it seems the stack format got > set, changed, then mostly reverted back, with this code being the last > piece missing from 2009. The commit to isohdpfx.S of 2009-05-31 looks incomplete. The sequence of the stack pointers was swapped, but the sequence of stack pushes was not.