Re: sparc64 network autoconfiguration

[Toomas Soome]

> On 18. märts 2016, at 13:25, Andrei Borzenkov <address@hidden> wrote:
> 
> On Fri, Mar 18, 2016 at 1:14 PM, Toomas Soome <address@hidden> wrote:
>> 
>>> On 18. märts 2016, at 11:54, Andrei Borzenkov <address@hidden> wrote:
>>> 
>>> On Fri, Mar 18, 2016 at 12:49 PM, Stanislav Kholmanskikh
>>> <address@hidden> wrote:
>>>> Hi!
>>>> 
>>>> 
>>>> On 03/18/2016 11:30 AM, Andrei Borzenkov wrote:
>>>>> 
>>>>> On Fri, Mar 18, 2016 at 11:07 AM, Vladimir 'phcoder' Serbinenko
>>>>> <address@hidden> wrote:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Le ven. 18 mars 2016 08:30, Andrei Borzenkov <address@hidden> a
>>>>>> écrit :
>>>>>>> 
>>>>>>> 
>>>>>>> Documentation says
>>>>>>> 
>>>>>>> On sparc64 GRUB is unable to determine which server it was booted from.
>>>>>>> 
>>>>>>> Could someone clarify what it means here? sparc64 is ieee1275 that
>>>>>>> supports auto configuration for network boot - at least, it has code
>>>>>>> to do it. So far the only platform where it is not possible seems to
>>>>>>> be uboot (which is also missing from Platform limitations section).
>>>>>> 
>>>>>> 
>>>>>> AFAIR sparc 64 doesn't provide fields code for ieee1275 depends on.
>>>>>> Moreover
>>>>>> sparc64 doesn't support booting via dhcp and works thorough rarp instead
>>>>> 
>>>>> 
>>>>> 
>>>>> Strictly speaking they boot via bootparams protocol, RARP is used for
>>>>> initial IP auto-configuration. Sun/Oracle servers support DHCP boot
>>>>> for quite some time; actually it is mandatory for Solaris 11 AI
>>>>> (automated installer). I am not sure whether they export this
>>>>> information in OBP though.
>>>>> 
>>>>> Someone from Oracle listening here?
>>>> 
>>>> 
>>>> I can't say for Oracle HW in general, but on T4, T5, T7 machines booting 
>>>> via
>>>> DHCP/TFTP is supported, for example via 'boot net:dhcp'.
>>>> 
>>> 
>>> Sure, but is content of DHCP ACK available to GRUB (see
>>> grub-core/net/drivers/ieee1275/ofnet.c:grub_ieee1275_net_config_real())
>>> - i.e. can GRUB do autoconfiguration of network interface used to load
>>> it based on information from firmware?
>>> 
>> 
>> the ack is saved in /chosen-bootreply in forth code. (google 
>> /chosen-bootreply openboot does some hints in openboot source in 
>> coreboot.org).
>> 
> 
> We are currently looking for the following properties on /chosen/bootpath
> 
> bootp_response_properties[] =
>  {
>    { .name = "bootp-response", .offset = 0},
>    { .name = "dhcp-response", .offset = 0},
>    { .name = "bootpreply-packet", .offset = 0x2a},
>  };
> 
> 
> As I understand this does not cover sparc, it need additional code to
> parse different node, right?
> 

To be sure one really has to just verify what/how different it is. The thing 
is, much of the code around is based on opensourced T1/T2 sources and obviously 
have started to live life of its own but the core logic should be similar 
still. Also the T2 sources are still downloadable, even as searching out the 
actual download link may be a bit of the issue. 

rgds,
toomas