public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: David Brownell <david-b@pacbell.net>
Cc: linux-pm@lists.osdl.org, richard@hughsie.com
Subject: Re: suspend and hibernate nomenclature
Date: Sat, 20 May 2006 22:55:50 +0200	[thread overview]
Message-ID: <20060520205550.GA8490@elf.ucw.cz> (raw)
In-Reply-To: <200605201347.27957.david-b@pacbell.net>

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

Hi!

> > > > > ?? WOL is for different functionality, I'm afraid. Or do you know
> > > > > ethernet hub that automagically wakes machines when data come?
> > > > 
> > > > No, that's exactly what WOL is designed for.  A typical scenarios has
> > > > the adapter waking up when the incoming packet is unicast to the MAC
> > > > address of that host.  The hub/switch would act normally.
> > > 
> > > I do not think WOL wakes that way. IIRC it needs magic ethernet
> > > packet.
> > 
> > That's right.  I don't remember what the contents need to be, but WOL 
> > doesn't work with any old ethernet packet.
> 
> You're both wrong.  Notice what "man ethtool" reports:

Ok, you are right and I was wrong....

>        wol p|u|m|b|a|g|s|d...
>               Set Wake-on-LAN options.  Not all devices support this.  The argument to this
>               option is a string of characters specifying which options to enable.
> 
>               p  Wake on phy activity
>               u  Wake on unicast messages
>               m  Wake on multicast messages
>               b  Wake on broadcast messages
>               a  Wake on ARP
>               g  Wake on MagicPacket(tm)
>               s  Enable SecureOn(tm) password for MagicPacket(tm)
>               d  Disable (wake on nothing).  This option clears all
>        previous options.

...I only knew about magicpacket-like stuff.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2006-05-20 20:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-07 18:02 suspend and hibernate nomenclature Richard Hughes
2006-05-08 15:05 ` Jordan Crouse
2006-05-08 16:09   ` Richard Hughes
2006-05-08 20:01 ` Pavel Machek
2006-05-14 15:32   ` Richard Hughes
2006-05-14 15:39     ` Pavel Machek
2006-05-14 21:17       ` Rafael J. Wysocki
2006-05-08 23:47 ` David Brownell
2006-05-09  7:38   ` Richard Hughes
2006-05-09 15:57     ` David Brownell
2006-05-16 20:40       ` Pavel Machek
2006-05-18 19:56         ` David Brownell
2006-05-18 20:50           ` Pavel Machek
2006-05-19  2:25             ` David Brownell
2006-05-20 17:20               ` Pavel Machek
2006-05-20 19:23                 ` Alan Stern
2006-05-20 20:47                   ` David Brownell
2006-05-20 20:55                     ` Pavel Machek [this message]
2006-05-21 15:35                       ` Alan Stern
2006-05-20 20:54                 ` David Brownell
2006-05-20 22:39                   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2006-05-16 20:47 Scott E. Preece

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=20060520205550.GA8490@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=david-b@pacbell.net \
    --cc=linux-pm@lists.osdl.org \
    --cc=richard@hughsie.com \
    /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