On Fri, Apr 12, 2024 at 02:10:30AM +0200, Konrad Dybcio wrote:
>
>
> On 4/12/24 01:49, Elliot Berman wrote:
> > On Thu, Apr 11, 2024 at 10:24:08PM +0200, Konrad Dybcio wrote:
> > >
> > >
> > > On 4/11/24 22:09, Elliot Berman wrote:
> > > > On Thu, Apr 11, 2024 at 10:05:30PM +0200, Konrad Dybcio
On 4/12/24 01:49, Elliot Berman wrote:
On Thu, Apr 11, 2024 at 10:24:08PM +0200, Konrad Dybcio wrote:
On 4/11/24 22:09, Elliot Berman wrote:
On Thu, Apr 11, 2024 at 10:05:30PM +0200, Konrad Dybcio wrote:
On 4/11/24 20:55, Elliot Berman wrote:
On Fri, Apr 05, 2024 at 10:41:29AM +0200, K
On Thu, Apr 11, 2024 at 10:24:08PM +0200, Konrad Dybcio wrote:
>
>
> On 4/11/24 22:09, Elliot Berman wrote:
> > On Thu, Apr 11, 2024 at 10:05:30PM +0200, Konrad Dybcio wrote:
> > >
> > >
> > > On 4/11/24 20:55, Elliot Berman wrote:
> > > > On Fri, Apr 05, 2024 at 10:41:29AM +0200, Konrad Dybcio
On 4/11/24 22:09, Elliot Berman wrote:
On Thu, Apr 11, 2024 at 10:05:30PM +0200, Konrad Dybcio wrote:
On 4/11/24 20:55, Elliot Berman wrote:
On Fri, Apr 05, 2024 at 10:41:29AM +0200, Konrad Dybcio wrote:
In preparation for parsing the chip "feature code" (FC) and "product
code" (PC) (esse
On Thu, Apr 11, 2024 at 10:05:30PM +0200, Konrad Dybcio wrote:
>
>
> On 4/11/24 20:55, Elliot Berman wrote:
> > On Fri, Apr 05, 2024 at 10:41:29AM +0200, Konrad Dybcio wrote:
> > > In preparation for parsing the chip "feature code" (FC) and "product
> > > code" (PC) (essentially the parameters th
On 4/11/24 20:55, Elliot Berman wrote:
On Fri, Apr 05, 2024 at 10:41:29AM +0200, Konrad Dybcio wrote:
In preparation for parsing the chip "feature code" (FC) and "product
code" (PC) (essentially the parameters that let us conclusively
characterize the sillicon we're running on, including vari
On Fri, Apr 05, 2024 at 10:41:29AM +0200, Konrad Dybcio wrote:
> In preparation for parsing the chip "feature code" (FC) and "product
> code" (PC) (essentially the parameters that let us conclusively
> characterize the sillicon we're running on, including various speed
> bins), move the socinfo ver
On Fri, Apr 05, 2024 at 10:41:29AM +0200, Konrad Dybcio wrote:
> In preparation for parsing the chip "feature code" (FC) and "product
> code" (PC) (essentially the parameters that let us conclusively
> characterize the sillicon we're running on, including various speed
> bins), move the socinfo ver
In preparation for parsing the chip "feature code" (FC) and "product
code" (PC) (essentially the parameters that let us conclusively
characterize the sillicon we're running on, including various speed
bins), move the socinfo version defines to the public header and
include some more FC/PC defines.