From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 2/2] console: usb: kbd: To improve TFTP booting performance
Date: Wed, 31 Jul 2013 12:36:00 +0200 [thread overview]
Message-ID: <201307311236.00255.marex@denx.de> (raw)
In-Reply-To: <1375266077.11294.10.camel@jilin-desktop>
Dear Jim Lin,
> On Fri, 2013-07-19 at 21:53 +0800, Marek Vasut wrote:
> > Dear Jim Lin,
> >
> > > On Fri, 2013-07-19 at 19:17 +0800, Wolfgang Denk wrote:
> > > > Dear Jim Lin,
> > > >
> > > > In message <1374226576-13401-2-git-send-email-jilin@nvidia.com> you
wrote:
> > > > > TFTP booting is slow when a USB keyboard is installed and
> > > > > stdin has usbkbd added.
> > > > > This fix is to change Ctrl-C polling for USB keyboard to every
> > > > > second when NET transfer is running.
> > > >
> > > > ...
> > > >
> > > > > +#ifdef CONFIG_CMD_NET
> > > > > +/* The period of time between two calls of usb_kbd_testc(). */
> > > > > +static unsigned long kbd_testc_tms;
> > > > > +#endif
Just use __maybe_unused here to squash the ifdef ;-)
[...]
> > I'll wait for v3. In the meantime, I homestly dont like having such hacks
> > on both sides, but I dont think much can be done about it. Maybe use
> > __maybe_unused for the net_busy_flag to drop the ifdef ?
>
> I don't quite understand what you wanted me to do.
> Could you give me an example? What to add and what to remove.
> Thanks.
>
> --nvpublic
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-07-31 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 9:36 [U-Boot] [PATCH v7 1/2] NET: Add net_busy_flag if CONFIG_USB_KEYBOARD is defined Jim Lin
2013-07-19 9:36 ` [U-Boot] [PATCH v7 2/2] console: usb: kbd: To improve TFTP booting performance Jim Lin
2013-07-19 11:17 ` Wolfgang Denk
2013-07-19 12:06 ` Jim Lin
2013-07-19 13:53 ` Marek Vasut
2013-07-31 10:21 ` Jim Lin
2013-07-31 10:36 ` Marek Vasut [this message]
2013-07-31 10:30 ` Jim Lin
2013-07-31 9:48 ` Jim Lin
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=201307311236.00255.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox