search for: firwmar

On Mon, Oct 31, 2016 at 1:34 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > Hi Alex, > > As you're well-aware, your commit > 8539b37acef73949861a16808b60cb8b5b9b3bab (drm/nouveau/gr: use > NVIDIA-provided external firmwares) broke tons of existing setups for > people who were using extracted firmware files (stored in the > "nouveau" firmware directory)

Some firmware images may be large (64K), so using kmalloc memory is inappropriate for them. Use vmalloc instead, to avoid high-order allocation failures. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: stable at vger.kernel.org --- Couldn't get video decoding started on a long-running system due to high-order allocation failures. This seems like a fine use-case for vmalloc.

Hi Alex, As you're well-aware, your commit 8539b37acef73949861a16808b60cb8b5b9b3bab (drm/nouveau/gr: use NVIDIA-provided external firmwares) broke tons of existing setups for people who were using extracted firmware files (stored in the "nouveau" firmware directory) as a result of nouveau's ctxsw fw being ... lacking. This is especially common on GK106's for some reason.

...PC's through the phone's switch port was unbearably slow, making it almost impossible to work. When plugging back PC's directly to the LAN speed was normal again. On my test setup with a single phone here a the office I don't have that problem. Is there a known issue with that firwmare version? Could the switch be playing foul? (a Netgear FSM-7326-PEU)

Hi guys, I have made a upgrade to my addpac ap200c, however it does not upload complete, now I can load addpac. Is there anyway that can I upload the old firwmare? Any help is appreciated. System Boot Loader, Version 2.2.5/DUAL(852) Copyright (c) by AddPac Technology Co., Ltd. Since 1999. System Bootstrap, Version 1.2 Decompressing the image: # -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipe...

...169 0000:01:00.0: eth1: RTL8168d/8111d at 0xffffc9000187c000, 00:0a:cd:1d:44:fe, XID 081000c0 IRQ 31 r8169 0000:01:00.0: eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko] ADDRCONF(NETDEV_UP): eth0: link is not ready device eth0 entered promiscuous mode r8169 0000:01:00.0: eth1: invalid firwmare r8169 0000:01:00.0: eth1: unable to load firmware patch rtl_nic/rtl8168d-1.fw (-22) r8169 0000:01:00.0: eth1: link down r8169 0000:01:00.0: eth1: link down ADDRCONF(NETDEV_UP): eth1: link is not ready r8169 0000:01:00.0: eth1: link up ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready e1000e: eth0...

...te12xp0: Missed interrupt. Increasing latency to 7 ms in order to compensate. Jul 15 13:15:31 comunicacion01-cl kernel: [ ? ?0.000000] wcte12xp0: Missed interrupt. Increasing latency to 6 ms in order to compensate. Jul 15 13:15:30 comunicacion01-cl kernel: [ ? ?0.000000] wcte12xp: VPMADT032 Loading firwmare... <6>wcte12xp0: Missed interrupt. Increasing latency to 5 ms in order to compensate. Jul 15 13:15:28 comunicacion01-cl kernel: [ ? ?0.000000] wcte12xp (vpm150m_cmd_dequeue): HW Resetting VPMADT032 ... Jul 15 13:15:28 comunicacion01-cl kernel: [ ? ?0.000000] 2222 2222 Jul 15 13:15:28 comunic...

I've been trying to get a Win 2000 RAS server working with my asterisk PBX for quite some time, to no avail. I've googled, I've tried loads of configurations, I've rewired phone lines, and still I am not winning the battle. Here's my config. PRI->T400P->Asterisk->T400P->Adtran 750(L36 Firmware)->RAS Server. I have 4 Zap channels signalled FXO_KS to the 750

...nitrd... I could rely on CONFIG_EXTRA_FIRMWARE... but I > thought I didn't need that as nouveau is compiled as a module and not into > the kernel :| OK, well if modules are loaded off the FS and not initrd, then you're good on that front, assuming you really do have the updated linux-firwmare (April 4 or later -- https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b14134583c2a15d4404695f72cb523daedb877ab). Lots of people use initrd without understanding how it works. So there are two issues here... #1: we should probably disable reverse prime if you...

...CONFIG_EXTRA_FIRMWARE... but I > > thought I didn't need that as nouveau is compiled as a module and not into > > the kernel :| > > OK, well if modules are loaded off the FS and not initrd, then you're good > on that front, assuming you really do have the updated linux-firwmare (April > 4 or later -- > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ > commit/?id=b14134583c2a15d4404695f72cb523daedb877ab). Lots of people use > initrd without understanding how it works. Yeah, my linux-firmware snapshot is the one up to https://git.k...

...is clean. The clicking sometimes sounds like crosstalk between both lines. After talking on irc with chan_capi's developper (kapejod) it seems the problem might originate from the Diva card. We are using a vanilla 2.6.7 kernel on debian unstable. We recently updated to use the very latest Diva firwmare and divactrl-2.1 without any effect on the problem. I suspect the problem might be related to the Diva 4BRI drivers in kernel 2.6.x as the problem seems to have started when switching from 2.4.x. Has someone had a similar experience? Is there any solution? Thanks in advance for your insight, --...

Hello, We are creating a web-based conferencing application using Asterisk as the voice conferencing server. This as an open source project. We are trying to determine if there is interest of the community and perhaps work together to improve the application. Using the web application, you can upload your powerpoint presentation, manage the participants in the conference thru the web interface

https://bugs.freedesktop.org/show_bug.cgi?id=103946 Bug ID: 103946 Summary: [nouveau] Slowish and rough graphical interface with GTX 1060 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

hi guys I've one box where I just yesterday upgraded Centos. I wonder if that kernel upgrade process might somewhat troublesome. After that upgrade UEFI boot fails with: Failed to set MokListRT: Invalid Parameter Something has gone seriously wrong: import_mok_state() failed : Invalid Parameter Has anybody seen that? And maybe know to fix it? many thanks, L.

...ssize_t r; > + if (fd < 0) { > + fprintf(stderr, "opening firmware file %s failed: %m\n", path); > + return 1; > + } > + r = read(fd, dest, len); > + close(fd); > + > + if (r != len) { Here ^^ > + fprintf(stderr, "reading firwmare file %s failed: %m\n", path); > + return 1; > + } > + > + return 0; > +} > + ... > +static void > +nv84_decoder_decode_bitstream_mpeg12(struct pipe_video_decoder *decoder, > + struct pipe_video_buffer *video_target, >...

...itial support (need external fuc) daa9ab5 drm/nv108/ce: enable copy engines a763951 drm/nv108/fifo: initial support a0f95f1 drm/nvf0/gr: remove a copy+pasto in ctx reglist 67af60f drm/nvc0-/gr: bring in some macros to abstract falcon isa differences 90d6db1 drm/nouveau/falcon: use vmalloc to create firwmare copies d96bf43 drm/nouveau/gem: remove (now) unneeded pre-validate fence sync cef9e99 drm/nouveau/ttm: explicitly wait for bo idle before memcpy buffer move 35b8141 drm/nouveau/ttm: explicity sync with kernel channel before moving buffer 3c57d85 drm/nouveau/ttm: tidy up creation of temporary buffe...

...: %m\n", path); >> + return 1; >> + } >> + r = read(fd, dest, len); >> + close(fd); >> + >> + if (r != len) { > Here ^^ Yes, in case that len is 2^64 - 1... but I'll change it :) > >> + fprintf(stderr, "reading firwmare file %s failed: %m\n", path); >> + return 1; >> + } >> + >> + return 0; >> +} >> + > ... >> +static void >> +nv84_decoder_decode_bitstream_mpeg12(struct pipe_video_decoder *decoder, >> + stru...

...>>> + } >>> + r = read(fd, dest, len); >>> + close(fd); >>> + >>> + if (r != len) { >> Here ^^ > > Yes, in case that len is 2^64 - 1... but I'll change it :) > >> >>> + fprintf(stderr, "reading firwmare file %s failed: %m\n", path); >>> + return 1; >>> + } >>> + >>> + return 0; >>> +} >>> + >> ... >>> +static void >>> +nv84_decoder_decode_bitstream_mpeg12(struct pipe_video_decoder *decoder, >>> +...

...t len) +{ + int fd = open(path, O_RDONLY | O_CLOEXEC); + ssize_t r; + if (fd < 0) { + fprintf(stderr, "opening firmware file %s failed: %m\n", path); + return 1; + } + r = read(fd, dest, len); + close(fd); + + if (r != len) { + fprintf(stderr, "reading firwmare file %s failed: %m\n", path); + return 1; + } + + return 0; +} + +static int +filesize(const char *path) +{ + int ret; + struct stat statbuf; + + ret = stat(path, &statbuf); + if (ret) + return ret; + return statbuf.st_size; +} + +static struct nouveau_bo * +nv84_l...

...t len) +{ + int fd = open(path, O_RDONLY | O_CLOEXEC); + ssize_t r; + if (fd < 0) { + fprintf(stderr, "opening firmware file %s failed: %m\n", path); + return 1; + } + r = read(fd, dest, len); + close(fd); + + if (r != len) { + fprintf(stderr, "reading firwmare file %s failed: %m\n", path); + return 1; + } + + return 0; +} + +static int +filesize(const char *path) +{ + int ret; + struct stat statbuf; + + ret = stat(path, &statbuf); + if (ret) + return ret; + return statbuf.st_size; +} + +static struct nouveau_bo * +nv84_l...