Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1563011 > unrolled thread
| Started by | Bjorn Andersson <bjorn.andersson@linaro.org> |
|---|---|
| First post | 2017-01-19 20:00 +0100 |
| Last post | 2017-01-19 20:00 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v4 1/3] firmware: add new extensible firmware API - drvdata Bjorn Andersson <bjorn.andersson@linaro.org> - 2017-01-19 20:00 +0100
| From | Bjorn Andersson <bjorn.andersson@linaro.org> |
|---|---|
| Date | 2017-01-19 20:00 +0100 |
| Subject | Re: [PATCH v4 1/3] firmware: add new extensible firmware API - drvdata |
| Message-ID | <t1q6d-5c3-5@gated-at.bofh.it> |
On Thu 12 Jan 07:02 PST 2017, Luis R. Rodriguez wrote: [..] > +Fallback mechanisms on the driver data API > +========================================== > + > +The old firmware API provided support for a series of fallback mechanisms. The > +new driver data API abandons all current notions of the fallback mechanisms, > +it may soon add support for one though. > + What will this fallback mechanism look like? Will it be fully compatible with the current userspace interfaces or will we forever have two duplicate systems for loading "firmware" in the kernel? Will the "sysdata" (or is it named "driver_data"?!) replace the firmware_class at any point in the future? Regards, Bjorn
Back to top | Article view | linux.kernel
csiph-web