[PATCH] SAM9 watchdog - supported on all SAM9 and CAP9 processors

[PATCH] SAM9 watchdog - supported on all SAM9 and CAP9 processors

[Andrew Victor]

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

The SAM9 watchdog driver is usable on the whole family of AT91SAM9 and
CAP9 processors.
Update the configuration to indicate this and allow the driver to be selected.

Signed-off-by: Andrew Victor <linux@maxim.org.za>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: sam9_wdt_config.patch --]
[-- Type: text/x-patch; name=sam9_wdt_config.patch, Size: 821 bytes --]

diff -urN -x CVS linux-2.6.28-rc3/drivers/watchdog/Kconfig linux-2.6/drivers/watchdog/Kconfig
--- linux-2.6.28-rc3/drivers/watchdog/Kconfig	2008-11-05 22:21:01.000000000 +0200
+++ linux-2.6/drivers/watchdog/Kconfig	2008-11-05 22:23:07.000000000 +0200
@@ -67,11 +67,11 @@
 	  system when the timeout is reached.
 
 config AT91SAM9X_WATCHDOG
-	tristate "AT91SAM9X watchdog"
-	depends on WATCHDOG && (ARCH_AT91SAM9260 || ARCH_AT91SAM9261)
+	tristate "AT91SAM9X / AT91CAP9 watchdog"
+	depends on ARCH_AT91 && !ARCH_AT91RM9200
 	help
-	  Watchdog timer embedded into AT91SAM9X chips. This will reboot your
-	  system when the timeout is reached.
+	  Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
+	  reboot your system when the timeout is reached.
 
 config 21285_WATCHDOG
 	tristate "DC21285 watchdog"

Re: [PATCH] SAM9 watchdog - supported on all SAM9 and CAP9 processors

[Andrew Morton]

On Wed, 5 Nov 2008 22:36:35 +0200
"Andrew Victor" <avictor.za@gmail.com> wrote:

> The SAM9 watchdog driver is usable on the whole family of AT91SAM9 and
> CAP9 processors.
> Update the configuration to indicate this and allow the driver to be selected.
> 
> Signed-off-by: Andrew Victor <linux@maxim.org.za>
> 

I queued your sam9-watchdog-update-for-moved-headers.patch for
immediate mainline merge by myself.

I queued this patch
(sam9-watchdog-supported-on-all-sam9-and-cap9-processors.patch) for
sending to Wim with a for-2.6.28 suggestion.

> [sam9_wdt_config.patch  text/x-patch (821B)]

sylpheed mucks that up.  text/plain attachments would be preferred,
please.  Inlined non-wordwrapped, non-tab-replaced, non-space-stuffed
text would of course be even better.

Re: [PATCH] SAM9 watchdog - supported on all SAM9 and CAP9 processors

[Andrew Victor]

hi Andrew,

> I queued your sam9-watchdog-update-for-moved-headers.patch for
> immediate mainline merge by myself.
>
> I queued this patch
> (sam9-watchdog-supported-on-all-sam9-and-cap9-processors.patch) for
> sending to Wim with a for-2.6.28 suggestion.

Thanks.


> sylpheed mucks that up.  text/plain attachments would be preferred,
> please.  Inlined non-wordwrapped, non-tab-replaced, non-space-stuffed
> text would of course be even better.

Unfortunately, gmail seems to mess up (ie, corrupt the whitespace of)
the inlined patches.
Maybe if I drop the ".patch" extension or use ".txt" it won't set the
content-type to text/x-patch.  Will try that next time.


Regards,
  Andrew Victor

Re: [PATCH] SAM9 watchdog - supported on all SAM9 and CAP9 processors

[Andrew Morton]

On Wed, 5 Nov 2008 22:58:45 +0200
"Andrew Victor" <avictor.za@gmail.com> wrote:

> > sylpheed mucks that up.  text/plain attachments would be preferred,
> > please.  Inlined non-wordwrapped, non-tab-replaced, non-space-stuffed
> > text would of course be even better.
> 
> Unfortunately, gmail seems to mess up (ie, corrupt the whitespace of)
> the inlined patches.

trust me, I noticed ;)


I have this queued:

From: Tim Hockin <thockin@google.com>

Signed-off-by: Tim Hockin <thockin@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 Documentation/email-clients.txt |   25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff -puN Documentation/email-clients.txt~documentation-email-clientstxt-add-some-info-about-gmail Documentation/email-clients.txt
--- a/Documentation/email-clients.txt~documentation-email-clientstxt-add-some-info-about-gmail
+++ a/Documentation/email-clients.txt
@@ -213,4 +213,29 @@ TkRat (GUI)
 
 Works.  Use "Insert file..." or external editor.
 
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Gmail (Web GUI)
+
+If you just have to use Gmail to send patches, it CAN be made to work.  It
+requires a bit of external help, though.
+
+The first problem is that Gmail converts tabs to spaces.  This will
+totally break your patches.  To prevent this, you have to use a different
+editor.  There is a firefox extension called "ViewSourceWith"
+(https://addons.mozilla.org/en-US/firefox/addon/394) which allows you to
+edit any text box in the editor of your choice.  Configure it to launch
+your favorite editor.  When you want to send a patch, use this technique.
+Once you have crafted your messsage + patch, save and exit the editor,
+which should reload the Gmail edit box.  GMAIL WILL PRESERVE THE TABS.
+Hoorah.  Apparently you can cut-n-paste literal tabs, but Gmail will
+convert those to spaces upon sending!
+
+The second problem is that Gmail converts tabs to spaces on replies.  If
+you reply to a patch, don't expect to be able to apply it as a patch.
+
+The last problem is that Gmail will base64-encode any message that has a
+non-ASCII character.  That includes things like European names.  Be aware.
+
+Gmail is not convenient for lkml patches, but CAN be made to work.
+
                                 ###
_