On Wed, Jun 02, 2021 at 08:07:07PM -0400, Gabriel Krisman Bertazi wrote: > I wasn't going to really oppose it from being a firmware but this > detail, if required, makes the whole firmware idea more awkward. If the > whole reason to make it a firmware is to avoid the module boilerplate, > this is just different boilerplate. Once again, I don't know about > precedent of kernel data as a module, and there is the problem with > Makefile rules to install this stuff, that I mentioned. > > We know we can get rid of the static call stuff already, since we likely > won't support more encodings anyway, so that would simplify a lot the > module specific code. Well, another thing we can do is a data-only module. That is a module that just contains the tables, with the core code doing a symbol_get on them.
