https://bugzilla.kernel.org/show_bug.cgi?id=74911 --- Comment #2 from Ivan Bulatovic <combuster@xxxxxxxxxxxx> --- > How long have you waited for? Trying to load a non-existent firmware file > may only time out after a minute or so. I've left it once for a while, but I'll test for how long and report back, seems to me it was about 4min. > > > This makes sense, there is no radeon/PITCAIRN_mc2.bin blob anywhere. At > > least not in linux-firmware branch. > > You can get it e.g. from: > > http://people.freedesktop.org/~agd5f/radeon_ucode/ > Thanx, got it! > > I have compiled radeon drivers into the kernel image itself, [...] > > It's recommended to build the radeon driver as a module instead and let the > firmware files be loaded from the initrd or normal filesystem. Well, if it was recommended I haven't saw that recommendation anywhere. Used to build an intel driver into kernel image itself, KMS kicks in as early as possible. I did the same with radeon, and it works for me great this whole time. Don't mean to be rude or anything, but I don't know if it is recommended (or desirable) to commit a piece of code to mainline that will _require_ a blob that can't be found in linux-firmware ? I'll see about the timeout and report back in. Thanks Michel -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
