.
I'm thinking about implementing asynchronous HDLC driver.
The patch has been generated against 2.4.4-ac6 tree. It should apply to
pure 2.4.4 as well. Protocol support is now split into separate files
hdlc_fr.c, hdlc_cisco.c etc.
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from
that were not mounted got trashed.
What gcc version did you use to compile it?
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
t code in some cases
(and it wasn't .c code fault but a compiler problem).
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
d save us (we can use pointers in such cases
as well, as some operations - downloading firmware or crypto keys - may have
very long data areas).
What do you think about it?
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
ARPHRD_HDLC only
in the header file for possible external drivers. It can then be removed
in 2.5.
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.
.
I think we need few ioctl calls: get + set media (int argument),
get + set speed (probably two - RX and TX), etc.
In my 2.4 HDLC stuff - to be published :-( - there something like that
(in private ioctl range, of course).
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list
kb changed, returned to upper layer for
re-inspection */
Of course, taps and bridges wouldn't be allowed to ask for re-inspection :-)
What do you think about this change? Does anything depend on the current
behavior?
--
Krzysztof Halasa
Network Administrator
-
To unsubs
*/
/* ARP cache control calls. */
/* 0x8950 - 0x8952 * obsolete calls, don't re-use */
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majo
.
While we're here, could we agree on the notion of raw hdlc, i.e. :
- no address, no command. crc present (ARPHRD_RAWHDLC ?);
- no address, no command, no crc (ARPHRD_PATHOLOGICHDLC ?).
Do we really need another ARPHRD for that?
BTW: What protocol(s) use such CRC-less HDLC?
--
Krzysztof Halasa
ple, which need
checking for max and min values and then setting variable length
(int/short/char).
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at ht
e. (CRC-16, CRC-32, no CRC)
Here - I think so. + good defaults.
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
that they are only
used with "acknowledged multiple frame operation". Isn't it for ISDN only?
With Frame Relay, we rather use unacknowledged transfers and UI frames.
Of course, if we have an implementation using t200, n200 or other
parameters, they should be added to the structure.
--
Krzysz
ernet-only interface is our ultimate goal,
I'll look at it again to see if I can stole some idea there.
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at ht
. The problem is I don't see here any advantages over many SIOCxxx
command codes, while there are disadvantages.
Simple things are IMHO better, and ioctl was designed to handle many
simple commands (instead of one complex).
Am I missing something?
--
Krzysztof Halasa
Network Administrator
o design good code and this is why we're all here.
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
o domains
- the core ioctl handler can still "verify" data area for the underlying
driver
--
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at ht
be enabled by its CONFIG_*.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
.
Well, who knows. The hardware side (config bits) are probably safe
and easy to verify, but depending on BIOS assigning address to inactive
device seems risky.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
-alike retransmissions etc.
I don't know if one can expect RTS to stay low all the time. Even
a simple /sbin/setserial from /etc/rc.* would drive it high for
a moment. I'm afraid the only way which makes sense may be using
a customized plug.
--
Krzysztof Halasa
-
To unsubscribe from this list: send
to CRTSCTS. The driver would, of course, need some real code
for that.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
a complete handshaking code.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
.
I bet all would share LED states. If you can use multiple keyboards
in legacy mode at all, of course.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
)
CLOCK_BASE = use_crystal_clock ? 24576000 : pci_clock_freq;
- return pci_module_init(pc300_pci_driver);
+ return pci_register_driver(pc300_pci_driver);
}
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
between devices in the system, so that although they are
shared interrupts, as few devices as possible get assigned to each
interrupt.
Correct. This scheme assumes at most 4 single-function devices
on the bus, otherwise INTs are shared.
--
Krzysztof Halasa
-
To unsubscribe from this list: send
for 'PnP OS installed'. Should I change that?
Most drivers already enable devices so it probably doesn't matter.
I would check it, though.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
is used by
only two devices, so the interrupt handler doesn't have too many devices
to check when an interrupt occours.
Right.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
it does.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Krzysztof Halasa [EMAIL PROTECTED] writes:
Remove duplicate prototypes for error(), gzip_mark() and gzip_release()
- they are first declared few lines earlier in all these files.
That's obviously
Signed-off-by: Krzysztof Halasa [EMAIL PROTECTED]
--
Krzysztof Halasa
-
To unsubscribe from
*if (a
\t*\s\s\s\sb)
another example:
\t*if (condition1 (a +
\t* b))
^^^ spaces, not tabs
I think the current CodingStyle is clear enough but improvements there
aren't prohibited.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe
algorithm, faster machine or slower disk
- slower than this cheap SATA with disabled NCQ (NV SATA) at least:
$ cat /sys/block/sda/device/model
Maxtor 6V250F0
Please note that aplication-level compression usually gives way
better results - the application knows much more.
--
Krzysztof Halasa
etc. There are other filesystems with
transparent compression, that's nothing new.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
(-xdev etc).
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ZFS.
Filesystem block hashes (checksums) and in-fs redundancy (using the
hashes to determine which copy of data is correct in case of
corruption). It would mean multi-device filesystem.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
Udo van den Heuvel [EMAIL PROTECTED] writes:
Yes, VIA Epia EN12000.
Interesting to check the riser card.
Unfortunately it turns out it's single slot only.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
becomes INT B at the MB connector and so on).
That means (unless INT rotations are configurable) you have to make
some (quite simple, in fact) modifications to the riser card :-(
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
universal dual+ PCI riser card have to use a PCI bridge
chip, and a bridge isn't a small 20 pin IC (I'd expect 144 pins or
so). Active or passive - doesn't matter.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
is probably older than your one, so I'd assume
it should work as well.
When you configure 0x13 and 0x14, both devices get IRQs - that means
the BIOS can see both of them.
The DN is the only variable so INT lines are hardwired on the riser card?
Yep. You just need a bit of soldering.
--
Krzysztof
by someone who knows
how to solder electronics.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
(which Linux could change anyway)
but it's a chipset-centric view (not very useful here).
Every PCI card have INT_A/B/C/D signals and they are (may be) remapped
on the riser card and on the motherboard.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
is
detected and supported, even if the riser card isn't the correct one
(= the card wouldn't work but it shows up).
You just have to connect that card's INT A to whatever the BIOS
wants and expects. That's it.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
mechanical problems with edge connector - PCI slot connections?
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
. Unless you can configure INT connections on the riser
card, of course.
You need DN19 for the second slot (and perhaps 10 would work with
double INTx rotation), that's fixed in the BIOS.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
require (different) soldering.
It's possible that the riser card includes a bridge, though. A bridge
chip can select devices differently and thus it can handle 32 devices.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
position).
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
by the BIOS.
I'd try this aluminum film trick. Just be careful, shorting wrong
traces can destroy the hardware. As I wrote, shorting the good ones
can make the system (temporarily) unusable.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
), it's used for
various purposes such as providing +12V to the device (and two pins
can supply more power than one - sure, it isn't the best idea).
I wouldn't touch that.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
- the request wasn't to change the default operation - just
add a
method of controlling things, so those minority of people who want the
control can have it.
No problem as long as open without CRTSCTS raises RTS by default.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe
CRTSCTS?
Because you'd break many devices otherwise.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
anymore, of course).
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 44 00 00 fe fd d3 00 a0
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 00
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
, unpack_to_rootfs()
does the job but returns bad gzip magic numbers error message - I think
I should change it to return that message only for first initramfs header
and return a success if some junk is spotted after a valid end of
compressed data.
Opinions?
--
Krzysztof Halasa
-
To unsubscribe from this list
:
What do you think?
In case someone wants to apply it (but something tells me it's not
that simple):
Signed-off-by: Krzysztof Halasa [EMAIL PROTECTED]
diff --git a/include/asm-generic/vmlinux.lds.h
b/include/asm-generic/vmlinux.lds.h
index 9fcc8d9..33e3036 100644
--- a/include/asm-generic
+84,6 @@ static unsigned long output_ptr = 0;
static void *malloc(int size);
static void free(void *where);
-static void error(char *m);
-static void gzip_mark(void **);
-static void gzip_release(void **);
static void puts(const char *);
--
Krzysztof Halasa
-
To unsubscribe from this list
more than two years old...
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
up using Linux (computers etc).
Or maybe e) to get a motherboard which isn't broken (with the kernel
you want to use).
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
double speed for the system time.
Right, I remember some reports about that, probably IOAPIC or other
HPET issues. Personally never seen that. Thus the suggestion of kernel
upgrade.
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
(of the
derivative work) may like it or not.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
MS Windows in your opinion have such a mixed
licence too? :-)
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
Adrian Bunk [EMAIL PROTECTED] writes:
Or that
OpenBSD != Linux kernel
was wrong since although they are not equal, they are related since they
are both open source operating systems.
BTW: never heard someone is using the FreeBSD version of Linux?
I did, not once :-)
--
Krzysztof Halasa
derived from other works, it's (C) MS and you get a licence for the
whole MS Windows from only MS.
You may have some additional rights and MS may have to acknowledge
additional contributors, based on their licences granted by those
contributors (such as using the original UCB licence).
--
Krzysztof
extra
rights do you have?
What you write is true for GPL, but it doesn't mean it's true
everytime. It's just that clause in the GPL.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
is just faulty.
The disc would need to be analyzed.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
I think.
That means email may be unreliable in such cases (except maybe when
both sides use UTF-8 and the patch contains only UTF-8), git/ftp/etc.
will be fine.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
: timeout while initializing card
+ printk(KERN_WARNING wanXL %s: timeout while initializing card
firmware\n, pci_name(pdev));
wanxl_pci_remove_one(pdev);
return -ENODEV;
Acked-by: Krzysztof Halasa [EMAIL PROTECTED]
Thanks
Adrian Bunk [EMAIL PROTECTED] writes:
This patch removes the EXPERIMENTAL option and all dependencies on
EXPERIMENTAL because they are pointless.
Unfortunately I have to agree. The only think it does is confusing
users, when they forget to enable it.
--
Krzysztof Halasa
-
To unsubscribe from
0WS mean 1 WS for 8-bit devices?).
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Pavel Machek [EMAIL PROTECTED] writes:
On Tue 2007-09-11 14:18:57, Krzysztof Halasa wrote:
I think 2.6.22 would be overkill, .23 - not sure.
I don't think this is -stable kind of bug.
Given the timeframe, I can only agree once again :-)
--
Krzysztof Halasa
-
To unsubscribe from this list
a difference at 0x1e only, that A0 00 at the end - who
knows (would require an analyzer).
and, if you tried upgrading or downgrading, if it worked.
I haven't tried it yet.
I guess chances for the last card are lower.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe
there.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
contact?
I'm not asking for something extraordinary, am I?
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
involved in receiving video from
a DV camera, using the new driver?
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
.
OTOH, it's no magic - they claim OHCI 1.1 and they do it. We don't
only know how to enable it with (only) software. I suspect all those
VT6306 could be upgraded as well.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
(and SCL) state in I^2C mode (I can blindly write to the
EEPROM and I can read the EEPROM data using GUID PROM register so
there is a workaround).
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
(and 6306) is
a common thing, or is it just an exception.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
really know.
VT6306 only supports 93c46 EEPROM so if the program says 24c01
you may want to force it (edit the source) and let me know.
VT6305 users may not bother, this chip doesn't support OHCI-1.1.
Not sure if anything like it ever existed, though.
--
Krzysztof Halasa
-
To unsubscribe from this list
service and is prohibited from using its INTx# pin [...]
But unfortunately that is rather irrelevant, since we see these
out-of-spec devices in the field today.
Right.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
).
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Kok, Auke [EMAIL PROTECTED] writes:
Don't work by default. pci=nomsi fixes the problem.
actually does not fix anything - it just works around it by falling
back to legacy interrupts.
Actually it does, fixes the problem by working around a bug :-)
Thanks for info.
--
Krzysztof Halasa
(rev a3)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
Additional details on request.
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
and RxD (for RS-232).
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
/Kconfig | 2 +-
drivers/crypto/ixp4xx_crypto.c | 12 ++--
drivers/net/wan/ixp4xx_hss.c| 2 +-
13 files changed, 59 insertions(+), 68 deletions(-)
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line unsubscribe
probably even much less time, it would be a good time
to find someone to maintain IXP4xx code. I will be publishing (from time
to time) my tree (I'm using the hw myself), so even simple
cherry-picking would probably make some sense.
--
Krzysztof Halasa
--
To unsubscribe from this list: send the line
themselves, I will
do the fbset part and maybe MPlayer's if the fb.h patch is ok.
All four patches change only files in drivers/video/intelfb/, except
patch 4/4 which also adds FB_VMODE_ODD_FLD_FIRST in include/linux/fb.h.
Tested on i915G in 1440x576 50 Hz (I) with PAL TV.
--
Krzysztof
Intel FB: whitespace, bracket and other clean-ups
Signed-off-by: Krzysztof Halasa [EMAIL PROTECTED]
--- a/drivers/video/intelfb/intelfb.h
+++ b/drivers/video/intelfb/intelfb.h
@@ -231,8 +231,8 @@ struct intelfb_hwstate {
struct intelfb_heap_data {
u32 physical;
u8 __iomem
Intel FB: obvious changes and corrections
Signed-off-by: Krzysztof Halasa [EMAIL PROTECTED]
--- a/drivers/video/intelfb/intelfb.h
+++ b/drivers/video/intelfb/intelfb.h
@@ -355,7 +355,10 @@ struct intelfb_info {
struct intelfb_output_rec output[MAX_OUTPUTS];
};
-#define IS_I9XX(dinfo
Intel FB: the chip adds two halflines automatically in interlaced mode,
force even line count for the right timings.
Signed-off-by: Krzysztof Halasa [EMAIL PROTECTED]
--- a/drivers/video/intelfb/intelfbhw.c
+++ b/drivers/video/intelfb/intelfbhw.c
@@ -317,6 +317,14 @@ int intelfbhw_validate_mode
Intel FB: allow odd- and even-field-first in interlaced modes, and
proper sync to vertical retrace
Signed-off-by: Krzysztof Halasa [EMAIL PROTECTED]
--- a/drivers/video/intelfb/intelfbhw.c
+++ b/drivers/video/intelfb/intelfbhw.c
@@ -376,7 +376,7 @@ int intelfbhw_pan_display(struct
; or
^
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
is it.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
extended ASCII?
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Jan Engelhardt [EMAIL PROTECTED] writes:
What we see here might not be ASCII, but VGA-specific color values.
It's just that I call it ASCII since it's the mirrored opposite of ANSI.
I see. Then perhaps VGA color value would be better.
--
Krzysztof Halasa
-
To unsubscribe from this list: send
in
a independent way, such as writel/readl/pci_map_* etc.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
at the same time and address, so no bit can be
first or last.
Once again, you shift left (towards MSBit), you multiply, shifting
right divides. At least as long as you limit it to a single byte.
Perhaps if you tell us what are you exactly trying to achieve...
--
Krzysztof Halasa
-
To unsubscribe
Jeremy Fitzhardinge [EMAIL PROTECTED] writes:
There is no such thing as bit-order. The data lines are numbered,
say, D0 - D31, with D0 being LSB (bit) and D31 MSB.
Uh-huh. Check out an IBM Power manual some time.
Some pointer maybe?
--
Krzysztof Halasa
-
To unsubscribe from this list
in the same natural bit order. Of course
swab32 will do as well.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
on the northbridge - should have
been 31 - 0, 30 - 1, etc...
I suspect the board wasn't able to run any OS, was it? :-)
Would make a real example of the different order of bits, though.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
I'd probably leave the thing as is (i.e., BSD/GPL
= in fact BSD), unless something like 50+% of the code is rewritten -
it's mostly their hard work after all, isn't it? Not legal
requirement, though.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
one if required.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
of course the licence contained such reservation.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
1 - 100 of 654 matches
Mail list logo
