[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e06668bf-f878-4a81-9f52-8fd047c1921c@lunn.ch>
Date: Thu, 14 Nov 2024 03:43:53 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Jacky Chou <jacky_chou@...eedtech.com>
Cc: "andrew+netdev@...n.ch" <andrew+netdev@...n.ch>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"robh@...nel.org" <robh@...nel.org>,
"krzk+dt@...nel.org" <krzk+dt@...nel.org>,
"conor+dt@...nel.org" <conor+dt@...nel.org>,
"p.zabel@...gutronix.de" <p.zabel@...gutronix.de>,
"ratbert@...aday-tech.com" <ratbert@...aday-tech.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: 回覆: [net-next 3/3] net:
ftgmac100: Support for AST2700
> > > - map = le32_to_cpu(rxdes->rxdes3);
> > > + map = le32_to_cpu(rxdes->rxdes3) | ((rxdes->rxdes2 &
> > > +FTGMAC100_RXDES2_RXBUF_BADR_HI) << 16);
> >
> > Is this safe? You have to assume older generation of devices will return 42 in
> > rxdes3, since it is not used by the hardware.
>
> Why does it need to return 42 in rxdes3?
> The packet buffer address of the RX descriptor is used in both software and hardware.
42 is just a random value. The point is, what do older generation of
devices return here? Some random value? Something well defined?
You basically need to convince us that you are not breaking older
systems by accessing registers which they do not have. Describe in the
commit message how you know this is safe, what testing you have done
etc.
Andrew
Powered by blists - more mailing lists