All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Bug report: PXE blocksize
Date: Mon, 30 Aug 2010 02:06:02 +0200	[thread overview]
Message-ID: <4C7AF5EA.5020305@gmail.com> (raw)
In-Reply-To: <D1A3B6E525F5F943AB9D12DED819DD5F013EAFBF@NYCMBX3.winmail.deshaw.com>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

On 08/27/2010 05:57 PM, Turner, Ian wrote:
> Hello list,
>
> There seem to be a couple of problems with this variable:
>
> 1. The variable name in the code is pxe_blksize, whereas the info file references net_pxe_blksize.
>   
Fixed. Thanks
> 2. Changing the blocksize from within a config file which is itself sourced from TFTP breaks the transfer of the remainder of that file, because grub_pxe_read() references the grub_pxe_blksize variable at each packet.
>   
> Issue #2 can be resolved just by changing the grub_pxe_read() reference to grub_pxe_blksize to reference data->block_size instead.
>   
I don't see where you mean. The only reference to pxe_blksize I see in
pxefs_read is following:
      o.packet_size = grub_pxe_blksize;
      grub_pxe_call (GRUB_PXENV_TFTP_OPEN, &o);
Which is called only when reopening file. Could you retry pulling? Now
newreloc is merged into mainline so you can just pull mainline.
> This is in the newreloc branch.
>
> Cheers,
>
> --Ian
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2010-08-30  0:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 15:57 Bug report: PXE blocksize Turner, Ian
2010-08-30  0:06 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-08-30 14:52   ` Turner, Ian
2010-09-02 22:01     ` Vladimir 'φ-coder/phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C7AF5EA.5020305@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.